Event Telemetry: Difference between revisions
(MOAR infos) |
(→Communication: links) |
||
Line 47: | Line 47: | ||
= Communication = | = Communication = | ||
* Conversation about Event telemetry on fhr-dev: https://mail.mozilla.org/listinfo/fhr-dev | * Conversation about Event telemetry on fhr-dev: https://mail.mozilla.org/listinfo/fhr-dev | ||
* IRC: #telemetry, #datapipeline, #metrics | * IRC: #telemetry, #datapipeline, #metrics | ||
* Slack: #fx-metrics | |||
* [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]] |
Revision as of 22:09, 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
- IRC: #telemetry, #datapipeline, #metrics
- Slack: #fx-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)