Design a metrics monitoring system
Collect metrics from millions of servers, store them as time series, draw dashboards and fire alerts, like Datadog or Prometheus.
Functional requirements
- Agents send metrics every 10 seconds
- Dashboards query and graph any metric
- Alert rules notify on-call engineers
Non-functional requirements
- Ingestion never drops data under load
- Dashboards render in under 1 second
- Alerts fire within a minute
Scale
- 10M data points per second
- 1B active time series
- Data kept for one year
How you’ll be scored
10 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design a metrics monitoring system”, that starts with: Agents send metrics every 10 seconds; Dashboards query and graph any metric; Alert rules notify on-call engineers. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (10M data points per second; 1B active time series; Data kept for one year) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: Ingestion never drops data under load; Dashboards render in under 1 second; Alerts fire within a minute. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe time series, ingestion and alerting here. This is a hard problem, so interviewers expect depth: what breaks first at this scale, how each failure is contained, and which trade-offs you accepted on purpose.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.