Platform/Features/Telemetry
| Feature | Status | ETA | Owner |
| Telemetry | Waiting on Server Setup (Corey Shields) | Unknown | Taras Glek |
Summary
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
Who's working on this?
- Lead Developer: Taras Glek
- Product Manager: Chris Blizzard
- QA: Unknown
- UX: Unknown
- Security: Unknown
- Services: Unknown
- Metrics: Unknown
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".
Waiting on Taras for definition.
Next Steps
Waiting on a server to be set up for collection. (Bug #636217)
- Start gathering data ASAP (simple counters). Going to piggyback on mfinkle's addon. (Week of April 11th)
- Integrate chromium's histogram smarts into telemetry. Get something ready to review to integrating into the product backend. (Week of April 18th)
- Set up server backend for receiving built-in telemetry. Metrics team. (April 18)
- Design & impl UI for opt-in. (???)
- Land it with required privacy bits. (Asa)
- Move on to field trials. (A/B testing)
Related Bugs & Dependencies
Need: Services plan, deployment plan, early items to measure.
Designs
Any and all mockups, design specs, tech specs, etc. Either inline or linked to.
Goals/Use Cases
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?
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?
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.
Other Documentation
Search List of macros used in Chrome
Legend (remove if you like)
| Healthy: feature is progressing as expected. | |
| Blocked: feature is currently blocked, but not yet at risk of missing this release. | |
| 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. |
Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.