Confirmed users
381
edits
Telemetry/Reboot: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
* Server should be bandwidth-limited, not CPU. | * Server should be bandwidth-limited, not CPU. | ||
* Server should make data available for map/reduce immediately. Fallback goal: 5min latency. In Q4 we'd like to use something like heka to make dashboards use live data(0min lag). | * Server should make data available for map/reduce immediately. Fallback goal: 5min latency. In Q4 we'd like to use something like heka to make dashboards use live data(0min lag). | ||
* Graphite reporting: valid packet rates for each channel, stats on packet sizes, etc | |||
Server Milestones: | Server Milestones: | ||
| Line 12: | Line 13: | ||
==Telemetry Dashboard== | ==Telemetry Dashboard== | ||
Dashboard(https://github.com/mozilla/telemetry-dashboard/) Milestones | Dashboard(https://github.com/mozilla/telemetry-dashboard/) Milestones: | ||
*Sep 1: Add median, percentiles, 90% ready | |||
*Sep 15: ^ finished | |||
Open bugs: https://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Telemetry%20Dashboard&list_id=7702794 | |||
Notes | ==Misc== | ||
Notes: | |||
* Original etherpad https://etherpad.mozilla.org/telemetry-reboot | * Original etherpad https://etherpad.mozilla.org/telemetry-reboot | ||