The Telemetry wiki page has more information about using Telemetry -- this page describes the 2015 project.

In 2015, we migrated Firefox Health Report data collection to the Telemetry system. At the same time, we made changes to Telemetry so that pings would be sent more frequently. We also updated the Data Pipeline that ingests and processes the data.

Dates

• Fx41 (2015-09-22): Started sending opt-out telemetry (base set) for 5% of the release population
• Fx42 (2015-11-03): Started sending opt-out telemetry (base set) for 100% of the release population
• Fx43 (2015-12-15): Stopped sending FHR v2 data

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

• Client pings (tree documentation)
• 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: Exploring with the Mozilla Data Pipeline Demo

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 4: https://bugzilla.mozilla.org/show_bug.cgi?id=1122482
• Bug tree, phase 3: https://bugzilla.mozilla.org/show_bug.cgi?id=1120356 (Done)
• 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

• Test cases document
• Spreadsheet to track testing

• 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
• Unified Telemetry/Data Continuity

• Kickoff document
  • "Query Requirements" section has list of sample queries/questions that get asked frequently of FHR data

• 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)