Unified Telemetry: Difference between revisions
Jump to navigation
Jump to search
(added bug spreadsheet) |
(forgot the actual spreadsheet link) |
||
| Line 10: | Line 10: | ||
* [https://docs.google.com/document/d/1IGpzsYGi_sq3YFQDAPyKOkU_BKvXAC95fZYA2i4ceVs/edit?usp=sharing Kickoff document] | * [https://docs.google.com/document/d/1IGpzsYGi_sq3YFQDAPyKOkU_BKvXAC95fZYA2i4ceVs/edit?usp=sharing Kickoff document] | ||
* Client work | * Client work | ||
** Backlog as spreadsheet, with estimates | ** Backlog as [https://docs.google.com/a/mozilla.com/spreadsheets/d/1yAJmgCGYyk1d7A41DZa653Z3u2AbH-kDWsO1vPSgbfE/edit?usp=sharing spreadsheet], with estimates | ||
** Bug tree, phase 3: https://bugzilla.mozilla.org/show_bug.cgi?id=1120356 | ** 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 2: https://bugzilla.mozilla.org/show_bug.cgi?id=1069869 (Done) | ||
Revision as of 16:54, 1 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
- 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)
- Client QA
- Format documentation