|
|
(43 intermediate revisions by 9 users not shown) |
Line 1: |
Line 1: |
| =Telemetry=
| | #REDIRECT [[Data]] |
| 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 [http://telemetry.mozilla.org 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==
| |
| ===For Firefox Devs===
| |
| | |
| '''Telemetry client-side:'''
| |
| * [https://developer.mozilla.org/en-US/docs/Performance/Adding_a_new_Telemetry_probe MDN: Adding a new Telemetry probe]
| |
| ** [[Firefox/Data_Collection|Data collection policy]]
| |
| * [https://ci.mozilla.org/job/mozilla-central-docs/Tree_Documentation/ Telemetry ping format (in-tree documentation)]
| |
| ** [https://github.com/mozilla/telemetry-server/blob/master/docs/PayloadFormat.md Older ping formats]
| |
| * Custom payloads uploaded by Telemetry:
| |
| ** [[Loop/Telemetry#Telemetry_Metrics|Loop (aka Firefox Hello) "ICE Failures" payload (with payload.reason="loop")]]
| |
| ** ...there are others
| |
| * [[Telemetry/Experiments|Telemetry Experiments]]
| |
| | |
| '''Analyzing Telemetry:'''
| |
| * [[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:
| |
| ** [http://www.robertovitillo.com/2015/01/16/next-gen-data-analysis-framework-for-telemetry/ Launch an ad-hoc analysis cluster]
| |
| ** [http://www.robertovitillo.com/2015/03/13/simple-dashboards-with-scheduled-spark-jobs-and-plotly/ Scheduling a custom analysis job]
| |
| ** [[Telemetry/Quirks|Telemetry Quirks: things to watch out for when analysing Telemetry data]]
| |
| ** [[CloudServices/DataPipeline|Telemetry Server-side development documentation]]
| |
| | |
| '''Telemetry status:'''
| |
| * [[Telemetry/Errata|Telemetry Errata: outages & known issues with collected Telemetry data]]
| |
| * [https://twitter.com/MozTelemetry Telemetry Twitter account]
| |
| * [http://ec2-50-112-66-71.us-west-2.compute.amazonaws.com:4352/# Heka dashboard showing Telemetry health], in particular the page showing [http://ec2-50-112-66-71.us-west-2.compute.amazonaws.com:4352/#sandboxes/TelemetryChannelMetrics60DaysAggregator/outputs/TelemetryChannelMetrics60DaysAggregator.nightly.cbuf submission rates & sizes]
| |
| | |
| '''New "unified" Telemetry that replaces FHR:'''
| |
| * [http://anthony-zhang.me/blog/telemetry-demystified/ Unified Telemetry overview #1]
| |
| * [[Unified_Telemetry|Overview #2]]
| |
| ** Unification progress: [https://bugzilla.mozilla.org/show_bug.cgi?id=1122515 tracking bug]
| |
| | |
| '''Code:'''
| |
| * [http://mxr.mozilla.org/mozilla-central/source/toolkit/components/telemetry/ Telemetry code in desktop Firefox]
| |
| * [https://github.com/mozilla/telemetry-dashboard/ Telemetry dashboard code]
| |
| * [https://github.com/mozilla/telemetry-server/ AWS Telemetry backend code] - soon to be superceded by the next generation backend
| |
| ** [https://github.com/mozilla/telemetry-aggregator Telemetry backend code for aggregating histograms]
| |
| | |
| ===For Firefox Users===
| |
| * [https://support.mozilla.org/kb/send-performance-data-improve-firefox Mozilla Support: Send performance data to Mozilla to help improve Firefox]
| |
| * [https://support.mozilla.org/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 ==
| |
| Telemetry client (in product) bugs should be filed in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=Telemetry Toolkit::Telemetry].
| |
| | |
| Telemetry dashboard bugs should be filed in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=Telemetry%20Dashboard Webtools::Telemetry Dashboard]
| |
| | |
| Telemetry data related bugs should be filed in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=Telemetry%20Server Webtools::Telemetry Server]
| |
| | |
| == Tracking Bugs ==
| |
| Open Telemetry bugs are usually organized as a blocker for one of the following tracking bugs:
| |
| * [https://bugzilla.mozilla.org/show_bug.cgi?id=1121467 Desired Telemetry measurements / probes]
| |
| * [https://bugzilla.mozilla.org/show_bug.cgi?id=1105864 Telemetry data quality issues]
| |
| * [https://bugzilla.mozilla.org/show_bug.cgi?id=1210637 Tracking for desired Telemetry dashboards]
| |
| * [https://bugzilla.mozilla.org/show_bug.cgi?id=1201022 Unified Telemetry cleanup work]
| |
| * [https://bugzilla.mozilla.org/show_bug.cgi?id=1220718 Telemetry ping size issues]
| |
| * [https://bugzilla.mozilla.org/show_bug.cgi?id=1226137 Tracking about:telemetry work and improvements]
| |
| | |
| ==Communication==
| |
| {| class="wikitable fullwidth-table"
| |
| ! Communication Type !! Mechanism !! Audience
| |
| |-
| |
| | Asking questions|| #telemetry on [https://wiki.mozilla.org/IRC irc.mozilla.org] || devs
| |
| |-
| |
| | General discussion || [https://lists.mozilla.org/listinfo/dev-platform dev-platform] and [https://mail.mozilla.org/listinfo/fhr-dev fhr-dev] list || devs
| |
| |-
| |
| | Announcements || [https://lists.mozilla.org/listinfo/dev-platform dev-platform], [https://lists.mozilla.org/listinfo/dev-planning dev-planning] lists || all
| |
| |}
| |
| | |
| ==People==
| |
| {| class="wikitable fullwidth-table"
| |
| | 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:
| |
| * [[Performance/Telemetry|Performance/Telemetry page]]
| |
| * [[Program_Management/Programs/Telemetry/Probe_Implementation|Probe implementation]]
| |
| * [[Privacy/Reviews/Telemetry|Telemetry Privacy Review]]
| |
| * [[QA/Telemetry|Telemetry Experiments QA]]
| |