Design a metrics monitoring and alerting system at scale — requirements, capacity, and trade-offs.
Skip to solution
KEEP THE
hardSystem Design
How would you design a metrics monitoring and alerting system?
0 views
01
Understand the problem
system-designcase-study
02
Attempt it yourself
Sketch your approach before reading the solution — that's what interviews test.
Nudge consolestandby
Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.
03
Study the solution
Design Metrics Monitoring & Alerting
Ingest 10M metrics/s, store for 90d, alert in <1m.
| Stage | Tech |
|---|---|
| Ingest | Kafka + OpenTelemetry OTLP + throttle |
| Storage | TSDB Prometheus/M3/ClickHouse sharded by metric+labels |
| Alerting | SLO burn rate window 5m for 2m + `Ale |
Solution ready — 2 min read
Classified // press E to declassify
04
Join the discussion
Discussion (0)
Sign in to join the discussion.
No responses yet. Be the first to share what you think.
Transmission complete // awaiting log
KEEP THE
STREAK ALIVE.
Dossier 92 of 99 decoded in the System Design track. One more won't hurt.