Unified Telemetry: Difference between revisions
Jump to navigation
Jump to search
m (→Resources: Add explanatory text to links) |
(→Data validation: Add monitor links) |
||
| Line 31: | Line 31: | ||
** default browser status | ** default browser status | ||
** places counts | ** places counts | ||
=== Client Testing === | |||
=== Monitoring === | * [https://docs.google.com/document/d/10sZICCbsfcSTF3RPyeVDskSI9-I2E4iApmShmIWSLfg/edit#heading=h.a6hfij6xookn Test cases document] | ||
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1YxqvjRJuuIPRegNXAFCLHA7_56vhQ6leaZLaLeFqyxY/edit#gid=0 Spreadsheet to track testing] | |||
=== Monitoring Tasks === | |||
* https://bugzilla.mozilla.org/show_bug.cgi?id=1147395 (Compare a few telemetry measurements between "saved-session" and "main" pings) | * https://bugzilla.mozilla.org/show_bug.cgi?id=1147395 (Compare a few telemetry measurements between "saved-session" and "main" pings) | ||
* https://bugzilla.mozilla.org/show_bug.cgi?id=1129185 (Reporting to make sure we don't have broken or incomplete session fragment chains) | * https://bugzilla.mozilla.org/show_bug.cgi?id=1129185 (Reporting to make sure we don't have broken or incomplete session fragment chains) | ||
* https://bugzilla.mozilla.org/show_bug.cgi?id=1134669 (unified-FHR quality report: activity latency) | * https://bugzilla.mozilla.org/show_bug.cgi?id=1134669 (unified-FHR quality report: activity latency) | ||
=== | === Monitors === | ||
* [https:// | * [https://pipeline-prototype-cep.prod.mozaws.net/#plugins/filters/PrototypeSandbox-mreid_CountRecentByDocType Count Recent By Doc Type] | ||
* | * | ||
Revision as of 13:44, 5 May 2015
Overview
We're unifying the Telemetry and Firefox Health Report collection systems on the client, and sending them through one Data Pipeline.
Goals
- On the client, unify the telemetry and FHR measurement systems so that measurements do not have to be implemented more than once in different systems.
- Reduce the latency from the time a measurement occurs until it can be analyzed on the server.
- Increase the accuracy of measurements so that they can be better correlated with factors in the user environment such as the specific build, enabled addons, and other hardware or software factors.
Resources
- Kickoff document
- "Query Requirements" section has list of sample queries/questions that get asked frequently of FHR data
- Format documentation
Timeline
Client work
- Backlog as spreadsheet, with estimates
- Bug tree, phase 3: https://bugzilla.mozilla.org/show_bug.cgi?id=1120356
- Bug tree, phase 2: https://bugzilla.mozilla.org/show_bug.cgi?id=1069869 (Done)
- Bug tree, phase 1: https://bugzilla.mozilla.org/show_bug.cgi?id=1040800 (Done)
Data validation
Acceptance Criteria
- https://bugzilla.mozilla.org/show_bug.cgi?id=1134661 (An automated script to compare FHR v2 results and FHR-v4 for a sample of users)
- For beta period, rollup fields compare reasonably to v2
- # of sessions
- session lengths
- searches
- default browser status
- places counts
Client Testing
Monitoring Tasks
- https://bugzilla.mozilla.org/show_bug.cgi?id=1147395 (Compare a few telemetry measurements between "saved-session" and "main" pings)
- https://bugzilla.mozilla.org/show_bug.cgi?id=1129185 (Reporting to make sure we don't have broken or incomplete session fragment chains)
- https://bugzilla.mozilla.org/show_bug.cgi?id=1134669 (unified-FHR quality report: activity latency)