Event Telemetry: Difference between revisions
Jump to navigation
Jump to search
Gfritzsche (talk | contribs) (First pass on page contents) |
(MOAR infos) |
||
| Line 1: | Line 1: | ||
The [[Telemetry]] wiki page has more information about using Telemetry -- this page describes the | The [[Telemetry]] wiki page has more information about using Telemetry -- this page describes the Event Telemetry project. | ||
= Overview = | = Overview = | ||
| Line 8: | Line 8: | ||
=== Dates === | === Dates === | ||
* ...: Event data explorable in re:dash (from pre-release channels) | * ...: Event data explorable in re:dash (from pre-release channels) | ||
* '''Fx52''' (~2017-03-07): Event data collection implemented in Firefox Telemetry | * '''Fx52''' (~2017-03-07): Event data collection implemented in Firefox Telemetry | ||
| Line 25: | Line 24: | ||
= Project = | = Project = | ||
=== Deliverables === | === Deliverables === | ||
* | * | ||
=== Client work === | === Client work === | ||
| Line 46: | Line 37: | ||
=== Pipeline work === | === Pipeline work === | ||
* Bugzilla: http://mzl.la/1KWiNST | * Bugzilla: http://mzl.la/1KWiNST | ||
=== Event Implementation Plan === | |||
* [https://docs.google.com/document/d/1cFCymhLQE7qI-p_czzz9-KexCMMhnf9ezLTMkGAKj58/edit#heading=h.w4fgaxpswo List of Event groups, events, owners etc] | |||
=== Client Testing === | === Client Testing === | ||
| Line 52: | Line 46: | ||
= Communication = | = Communication = | ||
* Conversation about | * Conversation about Event telemetry on fhr-dev: https://mail.mozilla.org/listinfo/fhr-dev | ||
* Data verification meeting notes: https://etherpad.mozilla.org/fhr-v4-status | * Data verification meeting notes: https://etherpad.mozilla.org/fhr-v4-status | ||
* IRC: #telemetry, #datapipeline, #metrics | * IRC: #telemetry, #datapipeline, #metrics | ||
* [ | * [https://docs.google.com/document/d/1P0BmMRLSglX9G53-j5udU5CnrwDaqcHKP5fFjU5hEwo/edit Weekly Meeting notes] | ||
* [[ | * [[Unified_Telemetry/Status_reports|EPM reports]] | ||
= Resources = | = Resources / Notes = | ||
* [https://docs.google.com/document/d/1IGpzsYGi_sq3YFQDAPyKOkU_BKvXAC95fZYA2i4ceVs/edit?usp=sharing Kickoff document] | * [https://docs.google.com/document/d/1IGpzsYGi_sq3YFQDAPyKOkU_BKvXAC95fZYA2i4ceVs/edit?usp=sharing Kickoff document] | ||
** "Query Requirements" section has list of sample queries/questions that get asked frequently of FHR data | ** "Query Requirements" section has list of sample queries/questions that get asked frequently of FHR data | ||
* [https://docs.google.com/document/d/1FI-jvzE4nVdas3e0o3QauNXUf5aQg9BGuXyVz0cDC1I/edit Event Telemetry Data sets discussion] | |||
= People and Roles = | = People and Roles = | ||
* Georg Fritzsche | * Georg Fritzsche | ||
* Alessio Placitelli, :Dexter (client data collection) | * Alessio Placitelli, :Dexter (client data collection) | ||
* Mark Reid (data pipeline, telemetry server) | * Mark Reid (data pipeline, telemetry server) | ||
* | * Roberto Vitillo | ||
* | * Sunah Suh (Analysis) | ||
* | * Rebecca Weiss (PM) | ||
* | * Ilana Segall (Analysis) | ||
* | * John Dorlus (Quality Engineering) | ||
* Roberto Vitillo (Spark analysis tool, telemetry data validation) | * Roberto Vitillo (Spark analysis tool, telemetry data validation) | ||
* Thomas Huelbert (project management) | * Thomas Huelbert (project management) | ||
Revision as of 22:06, 27 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: https://telemetry-dash.mozilla.org/
- re:dash event data tables
Project
Deliverables
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
Event Implementation Plan
Client Testing
Communication
- Conversation about Event 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
- Weekly Meeting notes
- EPM reports
Resources / Notes
- Kickoff document
- "Query Requirements" section has list of sample queries/questions that get asked frequently of FHR data
- Event Telemetry Data sets discussion
People and Roles
- Georg Fritzsche
- Alessio Placitelli, :Dexter (client data collection)
- Mark Reid (data pipeline, telemetry server)
- Roberto Vitillo
- Sunah Suh (Analysis)
- Rebecca Weiss (PM)
- Ilana Segall (Analysis)
- John Dorlus (Quality Engineering)
- Roberto Vitillo (Spark analysis tool, telemetry data validation)
- Thomas Huelbert (project management)