← All parts

End-to-End Design

Design a Metrics Monitoring System · Part 3
Problem context

Design a metrics monitoring system. Millions of hosts and services emit numeric measurements — request rates, latencies, queue depth, error counts — and engineers watch them on dashboards and get paged when something breaks.

In scope: ingesting metric points from many sources, storing them as queryable time-series, answering range queries for dashboards, and evaluating alert rules that page someone. Out of scope: log aggregation and distributed tracing (different systems with different storage models), the dashboard visualization frontend, and machine-learning anomaly detection.

What a strong answer sounds like

State the decision, connect it to a requirement, and name the tradeoff. Keep the design focused on the workload in the prompt.

Ready for the end-to-end design interview?

The AI interviewer asks about this part of Design a Metrics Monitoring System. The interviewer guides you through topics one by one.