Telemetry/Reboot

Goal: Fast, Robust server & frontend operational by Sep 31st able to accept and graph telemetry data. This means that as of Oct 1 http://metrics.mozilla.com/ will stop updating. Metrics should be able to retire telemetry portion of mango cluster in October.

Telemetry Backend

Server(https://github.com/mreid-moz/telemetry-server/) requirements:

• Ability to process 10x incoming packet rates of metrics telemetry infrastructure on a single AWS instance: 2400req/s with 30K HTTP POST packets. Fall
• 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).
• Graphite reporting: valid packet rates for each channel, stats on packet sizes, etc

Server Milestones:

• Sep 2: Ability temporarily(1 hour?) point telemetry dns at AWS, forwarding telemetry to metrics cluster. Ideally we'd be able to do this at bouncer level so no changes are needed to accomplish forwarding
• Sep 16: ^ should be feeding both servers (metrics and AWS) until cutover date.

Telemetry Dashboard

Dashboard(https://github.com/mozilla/telemetry-dashboard/) Milestones:

• Sep 1: Add median, percentiles, 90% ready
• Sep 15: ^ finished
• Sep 15: Produce a second set of dashboards(same codebase, probably different http server) that are being fed data from AWS

Open bugs: https://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Telemetry%20Dashboard&list_id=7702794

Misc

Notes:

• Original etherpad https://etherpad.mozilla.org/telemetry-reboot