Unified Telemetry

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
  • Client pings (tree documentation)
  • V2 - V4 mappings
  • Schema observed by pipeline

Milestones

Plan of record, subject to change if acceptance criteria are not met.

Dates

• 2015-05-11: 39 Beta
  • We start receiving Beta traffic
• 2015-06-29: 40 Beta, 39 Release
• 2015-08-11: 40 Release
  • v2 data stops
  • saved-sessions ping stops
  • Release population (opt-out) sends telemetry base data

Acceptance Criteria (Beta -> Release)

• metrics team OK
  • longitudinal data has internal consistency and consistency with v2: [https://bugzilla.mozilla.org

/show_bug.cgi?id=1169103 Tracking Bug 1169103]

• • executive dashboard (in particular MAU)
  • search analysis
• pipeline/ops team OK
  • No hourly rate spikes: Telemetry submission rate spikes every hour
• performance team OK
  • Telemetry Dashboard

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

Metrics Team Validation

• 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

• Test cases document
• Spreadsheet to track testing

Monitoring Tasks

• Compare a few telemetry measurements between "saved-session" and "main" pings
• Reporting to make sure we don't have broken or incomplete session fragment chains
• unified-FHR quality report: activity latency

Monitors

• Count Recent By Doc Type
• app.channel vs. environment.settings.update.channel

Investigations

• https://etherpad.mozilla.org/unified-telemetry-investigations

Analysis and Reporting

Tools

• Automated data dump for data validation exercise
• Spark
  • Make FHRv4 data available per client through Spark
• Stream processing on real time data
  • Exploring with the Mozilla Data Pipeline Demo
• Reporting using stream processing tools
  • Reprocessing and incremental processing architecture for reporting

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