Unified Telemetry

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.

Resources

• Kickoff document
  • "Query Requirements" section has list of sample queries/questions that get asked frequently of FHR data
• Format documentation
  • Client pings (tree documentation)
  • V2 - V4 mappings

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

Data validation

Client Testing

• Test cases document
• Spreadsheet to track testing

Analysis and Reporting

Tools

• Spark
• Stream processing on real time data
  • Exploring with the Mozilla Data Pipeline Demo
• Reporting using stream processing tools

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

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)