Event Telemetry: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Project: remove pipeline bugs link (was generic))
Line 34: Line 34:
* [https://docs.google.com/document/d/10sZICCbsfcSTF3RPyeVDskSI9-I2E4iApmShmIWSLfg/edit#heading=h.a6hfij6xookn Test cases document]
* [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]
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1YxqvjRJuuIPRegNXAFCLHA7_56vhQ6leaZLaLeFqyxY/edit#gid=0 Spreadsheet to track testing]
=== Pipeline work ===
* Bugzilla: http://mzl.la/1KWiNST


=== Event Implementation Plan ===
=== Event Implementation Plan ===

Revision as of 22:21, 29 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

Project

Deliverables

Client work

Client Testing

Event Implementation Plan

Communication

Resources / Notes


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)