Unified Telemetry: Difference between revisions
Jump to navigation
Jump to search
(Cleaned up and simplified) |
(Further simplified page) |
||
| Line 8: | Line 8: | ||
* Use a common data pipeline for client telemetry and service log data. | * Use a common data pipeline for client telemetry and service log data. | ||
= | === Documentation === | ||
* [https://ci.mozilla.org/job/mozilla-central-docs/Tree_Documentation/toolkit/components/telemetry/telemetry/index.html Client pings (tree documentation)] | |||
* [https://docs.google.com/spreadsheets/d/1bqamxVskDF7kQ6xL7S2BqY8TpngL-w41v6keiX_qByg/edit?usp=sharing V2 - V4 mappings] | |||
=== Analysis and Reporting === | |||
* Telemetry Dashboard (now using v4 unified telemetry data!): https://telemetry.mozilla.org/ | |||
* Launch a spark cluster: https://telemetry-dash.mozilla.org/ | |||
* Stream processing, heka reporting: [https://mana.mozilla.org/wiki/display/CLOUDSERVICES/Exploring+with+the+Mozilla+Data+Pipeline+Demo Exploring with the Mozilla Data Pipeline Demo] | |||
= Deliverables = | = Project = | ||
=== Deliverables === | |||
* Monitoring and alerting about pipeline health | * Monitoring and alerting about pipeline health | ||
* Basic tool support | * Basic tool support | ||
| Line 27: | Line 30: | ||
** Search analysis continues to work | ** Search analysis continues to work | ||
= Client work = | === Client work === | ||
* Backlog as [https://docs.google.com/a/mozilla.com/spreadsheets/d/1yAJmgCGYyk1d7A41DZa653Z3u2AbH-kDWsO1vPSgbfE/edit?usp=sharing 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 | ||
| Line 33: | Line 36: | ||
* Bug tree, phase 1: https://bugzilla.mozilla.org/show_bug.cgi?id=1040800 (Done) | * Bug tree, phase 1: https://bugzilla.mozilla.org/show_bug.cgi?id=1040800 (Done) | ||
= Pipeline work = | === Pipeline work === | ||
* Bugzilla: http://mzl.la/1KWiNST | * Bugzilla: http://mzl.la/1KWiNST | ||
=== Client Testing === | === Client Testing === | ||
* [https://docs.google.com/document/d/10sZICCbsfcSTF3RPyeVDskSI9-I2E4iApmShmIWSLfg/edit#heading=h.a6hfij6xookn Test cases document] | * [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] | * [https://docs.google.com/a/mozilla.com/spreadsheets/d/1YxqvjRJuuIPRegNXAFCLHA7_56vhQ6leaZLaLeFqyxY/edit#gid=0 Spreadsheet to track testing] | ||
= Communication = | = Communication = | ||
| Line 54: | Line 48: | ||
* IRC: #telemetry, #datapipeline, #metrics | * IRC: #telemetry, #datapipeline, #metrics | ||
* [[Unified Telemetry/Status reports]] | * [[Unified Telemetry/Status reports]] | ||
= Resources = | |||
* [https://docs.google.com/document/d/1IGpzsYGi_sq3YFQDAPyKOkU_BKvXAC95fZYA2i4ceVs/edit?usp=sharing Kickoff document] | |||
** "Query Requirements" section has list of sample queries/questions that get asked frequently of FHR data | |||
= People and Roles = | = People and Roles = | ||
Revision as of 00:13, 1 September 2015
Overview
We're unifying the Telemetry and Firefox Health Report collection systems on the client, and sending them through one Data Pipeline. To accomplish this on the client, we're migrating all of the FHR data to the Telemetry system. The new data pipeline has some features of the old telemetry pipeline as well as the cloud services data pipeline that we use to ingest server log data from Firefox services.
Goals for Unified Telemetry
- 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.
- Use a common data pipeline for client telemetry and service log data.
Documentation
Analysis and Reporting
- Telemetry Dashboard (now using v4 unified telemetry data!): https://telemetry.mozilla.org/
- Launch a spark cluster: https://telemetry-dash.mozilla.org/
- Stream processing, heka reporting: Exploring with the Mozilla Data Pipeline Demo
Project
Deliverables
- Monitoring and alerting about pipeline health
- Basic tool support
- Telemetry Dashboard works against new pipeline data
- Telemetry-dash (or new equivalent) can launch spark, heka reporting jobs
- Derived data sets
- Executive dashboard rollup
- 1% sample of clientIds for longitudinal analysis
- v2-v4 Data Continuity
- Executive dashboard continues to work
- Search analysis continues to work
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)
Pipeline work
- Bugzilla: http://mzl.la/1KWiNST
Client Testing
Communication
- Conversation about unified telemetry on fhr-dev: https://mail.mozilla.org/listinfo/fhr-dev
- Data verification meeting notes: https://etherpad.mozilla.org/fhr-v4-status
- IRC: #telemetry, #datapipeline, #metrics
- Unified Telemetry/Status reports
Resources
- Kickoff document
- "Query Requirements" section has list of sample queries/questions that get asked frequently of FHR data
People and Roles
- Georg Fritzsche (client data collection)
- Alessio Placitelli, :Dexter (client data collection)
- Mark Reid (data pipeline, telemetry server)
- Michael Trinkala, :trink (data pipeline, heka)
- Wesley Dawson, :whd (data pipeline operations)
- Daniel Thornton, :relud (data pipeline operations)
- Stuart Philp (test automation)
- Anthony Zhang (Telemetry dashboard)
- Roberto Vitillo (Spark analysis tool, telemetry data validation)
- Brendan Colloran (metrics team, data validation)
- Sam Penrose (metrics team, data validation)
- Thomas Huelbert (project management)
- Katie Parlante (eng manager)
- Benjamin Smedberg (project sponsor, data steward)