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.

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

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

Dashboard Milestones

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