<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div>Thanks Katie, <br><br>I see what you are saying, and that is certainly possible, though I want to be pretty explicit when the results are sent from the client to the content server. I can transform the data to a Heka friendly format server side.<br><br></div>I should have made clear the reason I included the URL. The Fx on iOS marketing snippet can display multiple versions of multiple links. <br><br></div>The decision table:<br><br></div>Is the user on Android in a browser other than Fennec?<br></div>Show a web friendly play store link (Link A)<br><br></div>Is the user on iOS?<br></div>Show a non-web friendly Apple app store link. (Link B)<br><br></div>Is the user in a desktop browser?<br></div>Show web friendly play store link (Link A) and a web friendly Apple app store link (Link C).<br><br></div>Each link is part of the same snippet, so I hope to include the snippet identifier, a link identifier (the URL seems like a good identifier), and whether the link is clicked.<br><br></div>Thanks again Katie,<br></div>Shane<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 26, 2015 at 8:39 PM, Katie Parlante <span dir="ltr"><<a href="mailto:kparlante@mozilla.com" target="_blank">kparlante@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Shane,<br>
<br>
The dashboard that makes use of this info is:<br>
<a href="https://kibana.fxa.us-west-2.prod.mozaws.net/#/dashboard/elasticsearch/Client" target="_blank">https://kibana.fxa.us-west-2.prod.mozaws.net/#/dashboard/elasticsearch/Client</a> Snippet<br>
<br>
I've put together a couple of one-off reports; I don't think any one else is looking at it regularly. We can change the format if need be.<br>
<br>
That said, your proposal causes some problems, as nested json is harder to consume in any of our tools -- the json blob needs special case code to be parsed (heka) or is basically inaccessible (kibana3). (Datadog and kibana4 probably fall somewhere in the middle: possible but painful).<br>
<br>
Suggestion: log a more compact, easy-to-parse-in-tools format. Don't include the url: it is not needed for stats and the id/url mapping can be managed elsewhere.<br>
...<br>
marketing: [android-sync:false,hello:true]<br>
...<br>
<br>
cc'ing trink, as he may have a different take.<br>
<br>
Cheers,<br>
Katie<div class="HOEnZb"><div class="h5"><br>
<br>
On 4/22/15 1:27 PM, Shane Tomlinson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Katie (& list),<br>
I am helping Jon Petto from the growth team integrate a new verification<br>
page snippet into the content server. Unlike our previous marketing<br>
snippet, the new snippet has two links instead of just one. I'd like to<br>
log metrics on each of these links. Our current schema [1] only allows a<br>
single marketing link to be logged, which is unfortunate.<br>
<br>
I want to change the format [2]. Are the `marketingLink`,<br>
`marketingType`, and `marketingClicked` fields consumed by anybody? If<br>
not, this will be easy. If so, it bit trickier.<br>
<br>
I propose to log something like the following snippet as part of the<br>
metrics that are sent to the /metrics endpoint:<br>
<br>
...<br>
marketing: [<br>
{<br>
id: 'android-sync',<br>
url: '<a href="https://play.google.com/somebiglongscarylink" target="_blank">https://play.google.com/somebiglongscarylink</a>',<br>
clicked: false<br>
},<br>
{<br>
id: 'hello',<br>
url: '<a href="https://hello.firefox.com" target="_blank">https://hello.firefox.com</a>',<br>
clicked: true<br>
}<br>
],<br>
...<br>
<br>
This would give us the ability to log an arbitrary number of marketing<br>
items, potentially across multiple screens.<br>
<br>
What do you think?<br>
<br>
Shane<br>
<br>
--------------------<br>
<br>
[1] -<br>
<a href="https://github.com/mozilla/fxa-content-server/blob/master/app/scripts/lib/metrics.js#L40-L42" target="_blank">https://github.com/mozilla/fxa-content-server/blob/master/app/scripts/lib/metrics.js#L40-L42</a><br>
[2] - <a href="https://github.com/mozilla/fxa-content-server/issues/2338" target="_blank">https://github.com/mozilla/fxa-content-server/issues/2338</a><br>
</blockquote>
</div></div></blockquote></div><br></div>