885467 - Recognize FFOS on Identity Dashboards

Status: RESOLVED FIXED

(Mozilla Metrics :: Frontend Reports, defect)

Description

[Katie Parlante]

FFOS devices are now pointing at the main persona servers, so we should start seeing them in router-metrics.json, which feeds the "browserid" stats. Here's what we'd expect to see in router-metrics:

{"level":"info","message":"{\"browser\":\"Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0\",\"rp\":\"undefined://\",\"ip\":\"127.0.0.1\",\"type\":\"signin\",\"at\":\"Tue, 07 May 2013 16:01:59 GMT\"}","timestamp":"2013-05-07T16:01:59.053Z"}
{"level":"info","message":"{\"browser\":\"Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0\",\"rp\":\"undefined://\",\"ip\":\"127.0.0.1\",\"type\":\"signin\",\"at\":\"Tue, 07 May 2013 16:03:30 GMT\"}","timestamp":"2013-05-07T16:03:30.864Z"}
{"level":"info","message":"{\"browser\":\"Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0\",\"rp\":\"undefined://\",\"ip\":\"127.0.0.1\",\"type\":\"signin\",\"at\":\"Wed, 08 May 2013 00:55:01 GMT\"}","timestamp":"2013-05-08T00:55:01.867Z"}
{"level":"info","message":"{\"browser\":\"Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0\",\"rp\":\"undefined://\",\"ip\":\"127.0.0.1\",\"type\":\"signin\",\"at\":\"Wed, 08 May 2013 00:55:51 GMT\"}","timestamp":"2013-05-08T00:55:51.675Z"}

Here's a link to the relevant browserid code:
https://github.com/mozilla/browserid/blob/dev/lib/metrics.js#L89

I'm not at all familiar with Kettle, but looks like the etl processing might do some matching against a list of browsers. If I'm not mistaken, these are the scripts running on the new AWS setup: https://github.com/mozilla/identity-ops/tree/master/chef/cookbooks/persona-metrics/files/default/opt/bid_metrics

As Annie helpfully pointed out: Firefox OS is not really a "browser" it is an OS, and our UA string does not list an OS in the OS field of the UA string: http://lawrencemandel.com/2012/07/27/decision-made-firefox-os-user-agent-string/

Comment 1

[mroldan]

Katie
Is it possible to infer "FFOS" just by looking at the UA part of the router-metric file? How would I do that?
According to this: https://bugzilla.mozilla.org/show_bug.cgi?id=885423#c6
I could involve the rp for drawing a conclusion, but we'd like to avoid mixing fields.

For example, in this line:
{"level":"info","message":"{\"browser\":\"Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0\",\"rp\":\"undefined://\",\"ip\":\"127.0.0.1\",\"type\":\"signin\",\"at\":\"Tue, 07 May 2013 16:01:59 

I would like to infer that we have a FFOS device just by looking at "Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0"

thanks!

Comment 2

[Katie Parlante]

Maria,

Yes, agreed, we shouldn't involve the rp when identifying FFOS (while the RP shows up as "undefined" at the moment, that could very well change).

Yes, I think you can infer that we have a FFOS device just by looking at "Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0"

Sorry I didn't get back to you more quickly!

Comment 3

[mroldan]

Hi, Katie,
great, I'll just look at the UA.

Now, how I know that this is FFOS? I mean, I cannot do something like

if UA="Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0" then "It's FFOS"
:)

Which part or parts in this UA should I check to know that this is FFOS?
thanks,

Comment 4

[Katie Parlante]

This is the code browserid uses for the client side kpi data that it collects:
https://github.com/mozilla/browserid/blob/dev/lib/coarse_user_agent_parser.js

You should be able to match this part of the sring: 'Mozilla/5.0 (Mobile; rv:'

Comment 5

[mroldan]

"Firefox Mobile (FFOS)" appears now as one more browser in the "Sign-ins per day broken down by browser" chart in the Identity Dashboard.
We have data for FFOS starting at July 11th.