Event Telemetry: Difference between revisions
Jump to navigation
Jump to search
(→Deliverables: !) |
(!) |
||
| Line 12: | Line 12: | ||
=== Goals for Event Telemetry === | === Goals for Event Telemetry === | ||
* Enable | * Standardized event format for all pings collecting events (Main Ping, Test Pilot, Shield, Sync, etc.) | ||
* | * Expand collection of UI Telemetry to support Product teams | ||
* Enable top line metrics for 2017 | |||
* Standardized support for analysis of events | |||
* API support in client for collecting event telemetry | |||
=== Documentation === | === Documentation === | ||
| Line 35: | Line 38: | ||
** Test Pilot submitting events (using common format) | ** Test Pilot submitting events (using common format) | ||
** Custom sync ping is submitting events (using common format) | ** Custom sync ping is submitting events (using common format) | ||
** Event | ** Event data tables available in re:dash | ||
** Event data accessible in Spark | ** Event data accessible in Spark | ||
* '''2017 Q1''' | * '''2017 Q1''' | ||
| Line 62: | Line 65: | ||
* [https://docs.google.com/document/d/1P0BmMRLSglX9G53-j5udU5CnrwDaqcHKP5fFjU5hEwo/edit Weekly Meeting notes] | * [https://docs.google.com/document/d/1P0BmMRLSglX9G53-j5udU5CnrwDaqcHKP5fFjU5hEwo/edit Weekly Meeting notes] | ||
* [[Unified_Telemetry/Status_reports|EPM reports]] | * [[Unified_Telemetry/Status_reports|EPM reports]] | ||
= People and Roles = | = People and Roles = | ||
Revision as of 09:58, 30 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
- Standardized event format for all pings collecting events (Main Ping, Test Pilot, Shield, Sync, etc.)
- Expand collection of UI Telemetry to support Product teams
- Enable top line metrics for 2017
- Standardized support for analysis of events
- API support in client for collecting event telemetry
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
- 2016 Q3
- Project kickoff
- Common Event Format
- Event registration mechanism
- Dataset strategy (Event Telemetry Data sets discussion)
- 2016 Q4
- Test Pilot submitting events (using common format)
- Custom sync ping is submitting events (using common format)
- Event data tables available in re:dash
- Event data accessible in Spark
- 2017 Q1
- Activity Stream submitting events (using common format) (Georg please fill out)
- Event store API (Georg please fill out)
- about:telemetry (Georg please fill out)
- Mobile plan (Q1/TBD)
- Some project (TBD) is on the main ping
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
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)