Telemetry: Difference between revisions

Jump to navigation Jump to search
1,878 bytes removed ,  26 August 2014
Clean up, link up new experiments page
(Clean up, link up new experiments page)
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 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.  
Telemetry is a joint project between Engineering and Metrics with Engineering owning the in product Telemetry client and Metrics owning the Telemetry server side.


==Accessing Telemetry Data==
==Accessing Telemetry Data==
Line 18: Line 16:
===Firefox Devs===
===Firefox Devs===
* [https://developer.mozilla.org/en-US/docs/Performance/Adding_a_new_Telemetry_probe MDN: Adding a new Telemetry probe]
* [https://developer.mozilla.org/en-US/docs/Performance/Adding_a_new_Telemetry_probe MDN: Adding a new Telemetry probe]
* [[Telemetry/Experiments|Telemetry Experiments]]


== Filing Bugs ==
== Filing Bugs ==
Line 38: Line 37:
  |-
  |-
  | General discussion || [https://lists.mozilla.org/listinfo/dev-platform dev-platform] list || devs
  | General discussion || [https://lists.mozilla.org/listinfo/dev-platform dev-platform] list || devs
|}
=== Minutes and Progress Reports  ===
{| class="wikitable collapsible" style="width: 100%"
! style="background-color: rgb(221, 221, 221);" | 2013
|-
|
* Thursday, Apr 3, 2013 - [[Telemetry/2013-04-03|Metrics/Telemetry]]
* Thursday, Mar 28, 2013 - Cancelled due to availability
* Thursday, Mar 21, 2013 - Cancelled due to Snappy work week
* Thursday, Mar 14, 2013 - Cancelled due to Snappy work week
* Thursday, Mar 7, 2013 - [[Telemetry/2013-03-07|Metrics/Telemetry]]
* Thursday, Feb 28, 2013 - [[Telemetry/2013-02-28|Metrics/Telemetry]]
* Thursday, Feb 21, 2013 - [[Telemetry/2013-02-21|Metrics/Telemetry]]
* Thursday, Feb 14, 2013 - [[Telemetry/2013-02-14|Metrics/Telemetry]]
* Thursday, Feb 7, 2013 - [[Telemetry/2013-02-07|Metrics/Telemetry]]
* Thursday, Jan 31, 2013 - Meeting cancelled due to availability. [[Telemetry/2013-01-31|Metrics/Telemetry status update]]
* Thursday, Jan 24, 2013 - [[Telemetry/2013-01-24-data-storage|Telemetry data storage]]
* Thursday, Jan 17, 2013 - [[Telemetry/2013-01-17|Metrics/Telemetry process review]]
|}
{| class="wikitable collapsible collapsed" style="width: 100%"
! style="background-color: rgb(221, 221, 221);" colspan="2" | 2012
|-
|
* Monday, Jun 11, 2012 - [[ProgramManagement/Programs/Telemetry Meetings/2012-06-11|Telemetry dashboard tracking and privacy]]
* Wednesday, May 16, 2012 - [[ProgramManagement/Programs/Telemetry/Meetings/2012-05-16|Perf/Metrics work week Telemetry meeting]]
|}
{| class="wikitable collapsible collapsed" style="width: 100%"
! style="background-color: rgb(221, 221, 221);" | 2011
|-
|
* Thursday, Oct 27, 2011 - [[ProgramManagement/Programs/Telemetry/Meetings/2011-10-27|Fixing Telemetry opt-in UI]]
|}
|}


Line 86: Line 51:
  | Client Engineering || Taras Glek, Nathan Froyd, Vladan Djeric
  | Client Engineering || Taras Glek, Nathan Froyd, Vladan Djeric
  |-  
  |-  
  | Server Engineering || Daniel Einspanjer
  | Server Engineering || Mark Reid, Jonas Jensen
|-
| Incoming Bug Triage || Taras Glek, Lawrence Mandel
|-
| Security ||
  |-  
  |-  
  | Privacy || Sid Stamm
  | Privacy || Sid Stamm
Confirmed users, Bureaucrats and Sysops emeriti
1,217

edits

Navigation menu