Event Telemetry: Difference between revisions
(→Deliverables: quarters) |
(→Deliverables: rearrange) |
||
Line 27: | Line 27: | ||
=== Deliverables === | === Deliverables === | ||
* Common Event Format (Q3) | * Common Event Format (Q3) | ||
* Event registration mechanism (Q3) | |||
* Test Pilot submitting events (using common format) (Q4) | * Test Pilot submitting events (using common format) (Q4) | ||
* Activity Stream submitting events (using common format) (Georg please fill out) | * Activity Stream submitting events (using common format) (Georg please fill out) | ||
* Dataset strategy (Q4) | * Dataset strategy (Q4) | ||
* Event datasets (in re:dash) (Q4) | * Event datasets (in re:dash) (Q4) | ||
* Event data accessible in Spark (Q4) | * Event data accessible in Spark (Q4) | ||
* Event store API (Georg please fill out) | * Event store API (Georg please fill out) | ||
* about:telemetry (Georg please fill out) | * about:telemetry (Georg please fill out) | ||
* Mobile plan (Q1/TBD) | * Mobile plan (Q1/TBD) | ||
* Project on main ping (TBD) | |||
=== Client work === | === Client work === |
Revision as of 22:54, 29 September 2016
The Telemetry wiki page has more information about using Telemetry -- this page describes the Event Telemetry project.
Overview
There is a common need across teams (fx-team, mobile, test-pilot, heartbeat, …) to have a mechanism for recording, storing, sending & analysing application usage in an event-oriented format. The Data Platform team wants to support this with a common API and mechanisms for dealing with the collected data, without owning the individual measurements. The solution here is to provide common client code, a standard data format, so we can come up with common processes and tooling for data pipeline & analysis work. Historically we already send a form of UITelemetry data, but the current format is too complicated to work with and to maintain.
Dates
- ...: Event data explorable in re:dash (from pre-release channels)
- Fx52 (~2017-03-07): Event data collection implemented in Firefox Telemetry
Goals for Event Telemetry
- Enable exploratory usage behavior analysis
- Enable event data collection from Firefox and addons
Documentation
Analysis and Reporting
- Raw data using a spark cluster (ATMO): https://analysis.telemetry.mozilla.org/
- re:dash event data tables (STMO): https://sql.telemetry.mozilla.org/
Project
Deliverables
- Common Event Format (Q3)
- Event registration mechanism (Q3)
- Test Pilot submitting events (using common format) (Q4)
- Activity Stream submitting events (using common format) (Georg please fill out)
- Dataset strategy (Q4)
- Event datasets (in re:dash) (Q4)
- Event data accessible in Spark (Q4)
- Event store API (Georg please fill out)
- about:telemetry (Georg please fill out)
- Mobile plan (Q1/TBD)
- Project on main ping (TBD)
Client work
Client Testing
Event Implementation Plan
Communication
- Conversation about Event telemetry on fhr-dev: https://mail.mozilla.org/listinfo/fhr-dev
- IRC: #telemetry
- Slack: #fx-metrics
- Weekly Meeting notes
- EPM reports
Resources / Notes
People and Roles
- Georg Fritzsche (Data Platform, lead)
- Alessio Placitelli, :Dexter (Data Platform)
- Mark Reid (Data Platform)
- Roberto Vitillo (Data Platform)
- Sunah Suh (Data Platform)
- Rebecca Weiss (PM)
- Ilana Segall (Analysis)
- John Dorlus (Quality Engineering)
- Thomas Huelbert (project management)