Telemetry: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 26: Line 26:
====Analyzing Telemetry:====
====Analyzing Telemetry:====
* [https://github.com/mozilla/telemetry-batch-view/blob/master/docs/choosing_a_dataset.md Choosing a Dataset]
* [https://github.com/mozilla/telemetry-batch-view/blob/master/docs/choosing_a_dataset.md Choosing a Dataset]
* [[Performance#Tools|List of Telemetry tools (dashboards, custom analyses, and others)]]
* [http://anthony-zhang.me/blog/telemetry-demystified/ Telemetry analysis & dashboarding overview]
* Writing custom analysis jobs:
* Writing custom analysis jobs:
** [[Telemetry/Custom analysis with spark|Writing custom analysis jobs with Spark]]
** [[Telemetry/Custom analysis with spark|Writing custom analysis jobs with Spark]]
** [http://www.robertovitillo.com/2015/01/16/next-gen-data-analysis-framework-for-telemetry/ Launch an ad-hoc analysis cluster]
** [https://wiki.mozilla.org/Telemetry/Custom_dashboards_with_re:dash Custom dashboards with re:dash]
** [http://www.robertovitillo.com/2015/03/13/simple-dashboards-with-scheduled-spark-jobs-and-plotly/ Scheduling a custom analysis job]
** [https://github.com/mozilla/telemetry-batch-view/blob/master/docs/longitudinal_examples.md Working with the longitudinal dataset]
** [[Telemetry/Quirks|Telemetry Quirks: things to watch out for when analysing Telemetry data]]
** [[Telemetry/Quirks|Telemetry Quirks: things to watch out for when analyzing Telemetry data]]
** [[CloudServices/DataPipeline|Telemetry Server-side development documentation]]
* Working with the longitudinal dataset:
** [https://gist.github.com/vitillo/627eab7e2b3f814725d2 Tutorial notebook]
** [https://github.com/mozilla/telemetry-batch-view/blob/master/docs/longitudinal_examples.md Examples]


====Telemetry status:====
====Telemetry status:====

Revision as of 16:42, 21 December 2016

Telemetry

It's helpful for Mozilla's engineers and decision-makers to be able to measure how Firefox behaves in the real world. The Telemetry feature provides this capability by sending performance and usage info to Mozilla. As you use Firefox, Telemetry measures and collects non-personal information, such as performance, hardware, usage and customizations. It then sends this information to Mozilla on a daily basis and we use it to improve Firefox.

Seeing the Collected Data

  • Instance Telemetry data (collected in your browser) can be viewed by typing about:telemetry into the Firefox URL bar.
  • Aggregate Telemetry data from all submissions can be viewed on the Telemetry dashboard at telemetry.mozilla.org.
  • Arbitrary custom analyses can be done via analysis.telemetry.mozilla.org.
  • Different datasets are available for SQL queries in our re:dash instance.

Documentation

For Firefox Devs

Telemetry client-side:

Telemetry back-end:

Analyzing Telemetry:

Telemetry status:

New "unified" Telemetry that replaced FHR:

Code:

For Firefox Users

Filing Bugs

Telemetry client (in product) bugs should be filed in Toolkit::Telemetry.

Telemetry dashboard bugs should be filed in Webtools::Telemetry Dashboard

Telemetry data related bugs should be filed in Webtools::Telemetry Server

Tracking Bugs

Open Telemetry bugs are usually organized as a blocker for one of the following tracking bugs:

Communication

Communication Type Mechanism Audience
Asking questions #telemetry on irc.mozilla.org devs
General discussion dev-platform and fhr-dev list devs
Announcements dev-platform, dev-planning lists all

People

Project Champion
Program Management
Product Benjamin Smedberg, Vladan Djeric
UX
Client Engineering Vladan Djeric, Georg Fritzsche, Alessio Placitelli
Server Engineering Mark Reid
Data Analysis Roberto Vitillo
Privacy Sid Stamm
Legal Jishnu Menon

Reference

Out of date:

Retrieved from "https://wiki.mozilla.org/index.php?title=Telemetry&oldid=1157610"