Event Telemetry: Difference between revisions
(→Documentation: !) |
(Update in-tree docs link) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
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. | 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. | Historically we already send a form of UITelemetry data, but the current format is too complicated to work with and to maintain. | ||
=== Goals for Event Telemetry === | === Goals for Event Telemetry === | ||
| Line 20: | Line 16: | ||
=== Documentation === | === Documentation === | ||
* [https://docs.google.com/document/d/1hNuS9lUJMvMqgntZXbFA6xZBU9zBpQgo7x73-sXKRpI/ Event Telemetry draft] | * [https://docs.google.com/document/d/1hNuS9lUJMvMqgntZXbFA6xZBU9zBpQgo7x73-sXKRpI/ Event Telemetry draft] | ||
* [https:// | * [https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/collection/events.html In-tree docs] | ||
* [https://docs.google.com/document/d/1cFCymhLQE7qI-p_czzz9-KexCMMhnf9ezLTMkGAKj58/edit#heading=h.w4fgaxpswo Table of projects that will be collecting Event telemetry] | * [https://docs.google.com/document/d/1cFCymhLQE7qI-p_czzz9-KexCMMhnf9ezLTMkGAKj58/edit#heading=h.w4fgaxpswo Table of projects that will be collecting Event telemetry] | ||
| Line 32: | Line 28: | ||
* '''2016 Q3''' | * '''2016 Q3''' | ||
** Project kickoff | ** Project kickoff | ||
** Common Event Format | ** Common Event Format design | ||
** Event registration mechanism | ** Event registration mechanism design | ||
** Dataset strategy ([https://docs.google.com/document/d/1FI-jvzE4nVdas3e0o3QauNXUf5aQg9BGuXyVz0cDC1I/edit Event Telemetry Data sets discussion]) | ** Dataset strategy ([https://docs.google.com/document/d/1FI-jvzE4nVdas3e0o3QauNXUf5aQg9BGuXyVz0cDC1I/edit Event Telemetry Data sets discussion]) | ||
* '''2016 Q4''' | * '''2016 Q4''' | ||
** Telemetry events on main pings implemented in Firefox | |||
** Activity Stream submitting events (using common format, in main ping) | |||
** Event data accessible in Spark | |||
** Generic Event data table available in re:dash | |||
** 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) | ||
* '''2017 Q1''' | * '''2017 Q1''' | ||
** | ** More custom pings submitting events (using common format) | ||
** | ** Non-specialized, analysis-oriented datasets available | ||
** Mobile plan (Q1/TBD) | ** Mobile plan (Q1/TBD) | ||
** Some project (TBD) is on the main ping | ** Some project (TBD) is on the main ping | ||
| Line 52: | Line 49: | ||
=== Client Testing === | === Client Testing === | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1302670 Bugzilla tracking] | * [https://bugzilla.mozilla.org/show_bug.cgi?id=1302670 Bugzilla tracking] | ||
= Communication = | = Communication = | ||
Latest revision as of 20:54, 19 May 2020
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.
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 design
- Event registration mechanism design
- Dataset strategy (Event Telemetry Data sets discussion)
- 2016 Q4
- Telemetry events on main pings implemented in Firefox
- Activity Stream submitting events (using common format, in main ping)
- Event data accessible in Spark
- Generic Event data table available in re:dash
- Test Pilot submitting events (using common format)
- Custom sync ping is submitting events (using common format)
- 2017 Q1
- More custom pings submitting events (using common format)
- Non-specialized, analysis-oriented datasets available
- Mobile plan (Q1/TBD)
- Some project (TBD) is on the main ping
Client work
Client Testing
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)