Telemetry dashboard - Differentiate Windows 8 Metro browser vs Desktop browser

RESOLVED FIXED in Backlogged - BZ

Status

Mozilla Metrics
Metrics Data Ping
RESOLVED FIXED
5 years ago
3 years ago

People

(Reporter: bbondy, Unassigned)

Tracking

unspecified
Backlogged - BZ
x86_64
Windows 8.1

Details

(Whiteboard: [Telemetry][metro-preview])

Attachments

(1 obsolete attachment)

(Reporter)

Description

5 years ago
We would like for the metro browser to show up as a new product in the "Application Name" drop down in the Telemetry dashboard.

From discussions in #metrics on IRC you mentioned that it would be easier for us to change the app id.  Also you asked that I file this bug so we can track any work needed on your end.

A little background information:
In Windows 8 we have both a Metro and a Desktop browser. The metro browser has a distinct widget layer (/windows/winrt, but borrowing some things from /windows) and a completely distinct front end. 

A typical user will access both browsers, but we'd like telemetry data to show up differently.

Comment 1

5 years ago
Lawrence - please weigh this against work on other asks for the quarter.
Status: NEW → ASSIGNED
Target Milestone: Unreviewed → Backlogged - BZ
This looks to be fairly important to me and should be a simple change in the client/server.

Taras - Do you agree with differentiating between Win8 Metro and Desktop?

Annie - Can you please get a quick sizing estimate for this work to confirm that it is a simple change?
Whiteboard: [Telemetry]
If Fx for Metro gets a unique app ID, it would be a very straightforward change for us to surface that.  We just need to tweak the aggregations and the dashboard spec not to filter that product out.

If a new app ID isn't appropriate for the product, then we'd have to understand how we'd distinguish it in the Telemetry payloads and do more investigation on how to surface it.

I am really hoping that a new app ID is appropriate because I am sure that people will eventually want to be seeing ADI and crashes and various other metrics on it, and most of those are driven off of app ID to distinguish between products.

Comment 4

5 years ago
It appears that the current plan is to have a separate runtime ID for the metro and desktop side. Note that this is still going to require future work in terms of ADI because you'd start getting separate update pings from the "metro side" and the "desktop side" of the same physical install, and the user may have both sides running simultaneously. But we can deal with that later!

Updated

5 years ago
Whiteboard: [Telemetry] → [Telemetry][metro-preview]

Comment 5

5 years ago
Created attachment 660050 [details] [diff] [review]
patch

http://mxr.mozilla.org/mozilla-central/search?string=ec8030f7-c20a-464f-9b0e-13a3a9e97384

Added where it seemed appropriate. I didn't mess with anything extension related.

Metro fx's application ini template is here:

http://mxr.mozilla.org/projects-central/source/elm/browser/metro/application.ini.in
Assignee: nobody → jmathies
Attachment #660050 - Flags: review?(benjamin)

Updated

5 years ago
Blocks: 790212

Comment 6

5 years ago
Comment on attachment 660050 [details] [diff] [review]
patch

sorry wrong bug
Attachment #660050 - Flags: review?(benjamin)

Updated

5 years ago
Assignee: jmathies → nobody

Updated

5 years ago
No longer blocks: 790212

Updated

5 years ago
Attachment #660050 - Attachment is obsolete: true

Comment 7

5 years ago
The new appid for metrofx is '99bceaaa-e3c6-48c1-b981-ef9b46b67d60'. This landed today on elm.

Comment 8

5 years ago
MetroFirefox is now available on the Application Name selector
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Updated

3 years ago
OS: Windows 8 Metro → Windows 8.1
You need to log in before you can comment on or make changes to this bug.