Closed
Bug 1122479
Opened 9 years ago
Closed 9 years ago
[meta] about:healthreport needs to be updated to work with Telemetry data.
Categories
(Firefox Health Report Graveyard :: Client: Desktop, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Dexter, Unassigned)
References
Details
(Keywords: meta, Whiteboard: [unifiedTelemetry] [measurement:client])
We will need to update about:healthreport to work with Telemetry data.
Comment 1•9 years ago
|
||
Per discussion today, this is bigger in scope then expected and needs some more break-down. *** Client-side work We need to update the self-support API. Currently it works from one blob of data. We want it work based on the current and historic ping data (180 days retention), so those have to be exposed in the ping API. We probably don't always want all the 180 days backlog. The "raw data" part probably needs pagination (e.g. one ping or day per page etc.). *** Page content The about:healthreport content script comes from server-side, the source is here: https://github.com/mozilla/fhr-jelly/tree/master It currently isn't owned so well, so we might have to pick that up ourselves or find someone to update it. That server-side content is currently requested from a non-version URL: datareporting.healthreport.about.reportUrl;https://fhr.cdn.mozilla.net/%LOCALE%/ ... we need to include at least version/build information in that URL. As the about:healthreport content comes from the server, we don't have to worry about string freezes. The logic in that content needs to be updated to work from the invidual pings collected from the updated API (instead of one blob).
Updated•9 years ago
|
Keywords: meta
Summary: about:healthreport needs to be updated to work with Telemetry data. → [meta] about:healthreport needs to be updated to work with Telemetry data.
Updated•9 years ago
|
Whiteboard: [rC] [unifiedTelemetry]
Updated•9 years ago
|
Whiteboard: [rC] [unifiedTelemetry] → [unifiedTelemetry] [measurement:client]
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•