On 4/26/15 1:12 PM, Shane Tomlinson wrote:
Thanks Katie,
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.
Makes sense; I'm agnostic to the format from client to content server.
FWIW, "heka-friendly" doesn't really describe my concern, its more about
having a plan for where/how the analysis happens. Indeed, heka has a lot
of flexibility if we're willing to write the additional processing code
for a custom format; kibana less so. Other tools will have different
tradeoffs, but will be more likely to process flat/tabular formats
without custom code than nested structures.
I should have made clear the reason I included the URL. The Fx on iOS
marketing snippet can display multiple versions of multiple links.
The decision table:
Is the user on Android in a browser other than Fennec?
Show a web friendly play store link (Link A)
Is the user on iOS?
Show a non-web friendly Apple app store link. (Link B)
Is the user in a desktop browser?
Show web friendly play store link (Link A) and a web friendly Apple app
store link (Link C).
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.
I see. I assume that means that in the desktop browser case use the same
marketing-snippet-id would be used for both entries.
I'll take a step back: Who will be consuming the data, and how will they
be consuming it? What questions do they want to ask using the data?
So far, we've just asked, "What is the click-through rate for each
'marketingtype'?" With the current format, that question is relatively
easy to answer in kibana.
I'm guessing the growth team would want to ask similar questions either
by url or by snippet id (or by the snippet id/url pairing). I'm also
guessing they don't want to use kibana for this, but will want a data feed.
Another proposal: create a separate message type for snippet-views, with
one message for each snippet entry. Include the id/url/clicked fields.
If segmentation data is needed, include those fields as well (or use a
common "session id" with the client-metrics message).
The tabular data for snippet-views can then be viewed/processed in
kibana (or output to another system) easily, and/or we can write a heka
filter to generate a tabular aggregated/rollup output for a bespoke
dashboard.
Cheers,
Katie
Thanks again Katie,
Shane
On Sun, Apr 26, 2015 at 8:39 PM, Katie Parlante <[email protected]
<mailto:[email protected]>> wrote:
Hi Shane,
The dashboard that makes use of this info is:
https://kibana.fxa.us-west-2.prod.mozaws.net/#/dashboard/elasticsearch/Client
Snippet
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.
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).
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.
...
marketing: [android-sync:false,hello:true]
...
cc'ing trink, as he may have a different take.
Cheers,
Katie
On 4/22/15 1:27 PM, Shane Tomlinson wrote:
Hey Katie (& list),
I am helping Jon Petto from the growth team integrate a new
verification
page snippet into the content server. Unlike our previous marketing
snippet, the new snippet has two links instead of just one. I'd
like to
log metrics on each of these links. Our current schema [1] only
allows a
single marketing link to be logged, which is unfortunate.
I want to change the format [2]. Are the `marketingLink`,
`marketingType`, and `marketingClicked` fields consumed by
anybody? If
not, this will be easy. If so, it bit trickier.
I propose to log something like the following snippet as part of the
metrics that are sent to the /metrics endpoint:
...
marketing: [
{
id: 'android-sync',
url: 'https://play.google.com/somebiglongscarylink',
clicked: false
},
{
id: 'hello',
url: 'https://hello.firefox.com',
clicked: true
}
],
...
This would give us the ability to log an arbitrary number of
marketing
items, potentially across multiple screens.
What do you think?
Shane
--------------------
[1] -
https://github.com/mozilla/fxa-content-server/blob/master/app/scripts/lib/metrics.js#L40-L42
[2] - https://github.com/mozilla/fxa-content-server/issues/2338
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
