Event Telemetry: Difference between revisions
Jump to navigation
Jump to search
(→Communication: links) |
(→Project: order if contents) |
||
| Line 34: | Line 34: | ||
* Bug tree, phase 2: https://bugzilla.mozilla.org/show_bug.cgi?id=1069869 (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) | * Bug tree, phase 1: https://bugzilla.mozilla.org/show_bug.cgi?id=1040800 (Done) | ||
=== Client Testing === | |||
* [https://docs.google.com/document/d/10sZICCbsfcSTF3RPyeVDskSI9-I2E4iApmShmIWSLfg/edit#heading=h.a6hfij6xookn Test cases document] | |||
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1YxqvjRJuuIPRegNXAFCLHA7_56vhQ6leaZLaLeFqyxY/edit#gid=0 Spreadsheet to track testing] | |||
=== Pipeline work === | === Pipeline work === | ||
| Line 40: | Line 44: | ||
=== Event Implementation Plan === | === Event Implementation Plan === | ||
* [https://docs.google.com/document/d/1cFCymhLQE7qI-p_czzz9-KexCMMhnf9ezLTMkGAKj58/edit#heading=h.w4fgaxpswo List of Event groups, events, owners etc] | * [https://docs.google.com/document/d/1cFCymhLQE7qI-p_czzz9-KexCMMhnf9ezLTMkGAKj58/edit#heading=h.w4fgaxpswo List of Event groups, events, owners etc] | ||
= Communication = | = Communication = | ||
Revision as of 22:12, 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)
Client Testing
Pipeline work
- Bugzilla: http://mzl.la/1KWiNST
Event Implementation Plan
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)