MozillaWiki

Platform/Features/Telemetry: Difference between revisions

Page Discussion

Platform/Features/Telemetry (view source)

Revision as of 21:18, 23 July 2012

1,077 bytes removed ,  23 July 2012
no edit summary
No edit summary
 
(14 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
{{FeatureStatus
|-
|Feature name=Telemetry
| style="font-weight: bold; background: #DDD;" | Feature
|Feature stage=Landed
| style="font-weight: bold; background: #DDD;" | Status
|Feature version=Firefox 7
| style="font-weight: bold; background: #DDD;" | ETA
|Feature health=OK
| style="font-weight: bold; background: #DDD;" | Owner
|Feature status note=Deployed, see [http://arewesnappyyet.com arewesnappyyet.com]
|-
}}
<section begin="status" />
{{FeatureTeam
| [[Platform/Features/Telemetry|Telemetry]]
|Feature product manager=Chris Blizzard
| {{StatusAtRisk|status=Waiting on Review}}
|Feature feature manager=Taras Glek
| May 23rd(cutoff for ff6)
|Feature lead engineer=Taras Glek
| Taras Glek
|Feature security lead=Curtis Koenig
<section end="status" />
|Feature privacy lead=Sid Stamm, Asa Dotzler
|-
|Feature qa lead=AndreiD
|}
|Feature ux lead=Alex Limi
|Feature additional members=Daniel Einspanjer (metrics), Graydon Hoare, Rob Sayre
}}
{{FeaturePageBody
|Feature overview=Telemetry allows Engineering to receive aggregate data of browser health in the field.  Think cache hit rates, page load times across all browser instances or anything else we're interested in.


== Summary ==
The goal for this feature is to give our developers the ability to know if changes they are making have wide-ranging positive and negative effects at scale.  Are users seeing better performance?
Telemetry allows Engineering to receive aggregate data of browser health in the field.  Think cache hit rates, page load times across all browser instances or anything else we're interested in.


== Team ==
Another goal of this is to give us easy-to-use infrastructure to learn about the structure of the Internet as a whole.  That is, how do we tune our browser based on what the Internet and Web do?
Who's working on this?
|Feature requirements=* Modify privacy policy(Asa)
 
* '''Lead Developer''': Taras Glek
* '''Product Manager''': Chris Blizzard
* '''QA''': Unknown
* '''UX''': Limi
* '''Security''': Curtis Koenig
* '''Services''': Unknown
* '''Metrics''': Daniel Einspanjer
* '''Privacy''': Asa Dotzler, [[User:Sidstamm|Sid Stamm]]
 
Another person worth talking to is Graydon, who filed the original bug, and Sayer who has strong opinions on the matter.
 
== Release Requirements ==
Complete checklist of items that need to be satisfied before we can call this feature "done".
 
* Modify privacy policy(Asa)
* Add UI (Mike Hommey)
* Add UI (Mike Hommey)


See https://bugzilla.mozilla.org/show_bug.cgi?id=659396 for ongoing telemetry enhancements.
See https://bugzilla.mozilla.org/show_bug.cgi?id=659396 for ongoing telemetry enhancements.
 
|Feature non-goals=This is not a system for gathering feedback from individual users.  It is a system for us to get aggregate health data about browsers in the field.  It's also a chance for us to run lightweight tests if we want to learn how certain settings will affect browser performance or user experience.  It is distinct from the Test Pilot program.
== Next Steps ==
|Feature security review=* [https://wiki.mozilla.org/Security/Reviews/Firefox6/ReviewNotes/telemetry Security Discussion/Review]
 
|Feature privacy review=* [[Privacy/Reviews/Telemetry|Privacy Review]]
* Set up official server backend for receiving built-in telemetry.  Metrics team.  (May 6)
|Feature implementation notes=* [https://bugzilla.mozilla.org/show_bug.cgi?id=585196 telemetry infrastructure]
 
* [https://bugzilla.mozilla.org/show_bug.cgi?id=652656 privacy policy update]
* Design & impl UI for opt-in. (limi & glandium)
 
* Land it with required privacy bits. (Asa)
 
* Move on to field trials. (A/B testing)
 
== Related Bugs & Dependencies ==
 
[https://bugzilla.mozilla.org/show_bug.cgi?id=585196 telemetry infrastructure]
 
[https://bugzilla.mozilla.org/show_bug.cgi?id=652656 privacy policy update]
 
[[Privacy/Reviews/Telemetry|Privacy Review]]


'''Need''': Services plan, deployment plan, early items to measure.
'''Need''': Services plan, deployment plan, early items to measure.
 
}}
== Designs ==
{{FeatureInfo
Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
|Feature priority=P1
 
|Feature roadmap=Platform
== Goals/Use Cases ==
|Feature list=Platform
 
|Feature engineering team=Automation and Tools
The goal for this feature is to give our developers the ability to know if changes they are making have wide-ranging positive and negative effects at scale.  Are users seeing better performance?
}}
 
{{FeatureTeamStatus
Another goal of this is to give us easy-to-use infrastructure to learn about the structure of the Internet as a whole.  That is, how do we tune our browser based on what the Internet and Web do?
|Feature security status=sec-review-complete
 
|Feature security health=OK
== Non-Goals ==
|Feature security notes=[[Security/Reviews/Firefox6/ReviewNotes/telemetry|Notes]]
This is not a system for gathering feedback from individual users.  It is a system for us to get aggregate health data about browsers in the field.  It's also a chance for us to run lightweight tests if we want to learn how certain settings will affect browser performance or user experience.  It is distinct from the Test Pilot program.
|Feature qa status=Signed off for release
 
}}
== Other Documentation ==
== Other Documentation ==
 
* [http://codesearch.google.com/codesearch?q=UMA_histogram&vert=chromium Search List of macros used in Chrome]
[http://codesearch.google.com/codesearch?q=UMA_histogram&vert=chromium Search List of macros used in Chrome]
* [http://src.chromium.org/viewvc/chrome/trunk/src/base/metrics/ Metrics code in Chrome]
 
[http://src.chromium.org/viewvc/chrome/trunk/src/base/metrics/ Metrics code in Chrome]
 
== Legend (remove if you like) ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status=&nbsp;}}
| Blocked: feature is currently blocked, but not yet at risk of missing this release.
|-
| {{StatusAtRisk|status=&nbsp;}}
| At Risk: feature is at risk of missing this release.
|-
| '''ETA'''
| Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.
|}
 
__NOTOC__
 
Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
 
[[Category:Features]]
[[Category:Firefox]]
[[Category:Performance]]
[[Category:Polish]]
[[Category:Priority 1]]
[[Category:Priority 2]]
[[Category:Priority 3]]
[[Category:Unprioritized]]
Tglek
Confirmed users
381

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/312176...453597"