Design a Monitoring Dashboard with Explicit Latency Goals

Design a monitoring dashboard that displays incoming measurements with attention to latency. Explain both how quickly new measurements become visible and how quickly a user can load or change a chart.

Requirements and Constraints

For a concrete practice scope, assume producers emit timestamped numeric measurements with a metric name and a set of labels. Users choose a metric, label filters, and a time range to view a chart. These input and interaction details are exercise assumptions; no fixed throughput, retention period, freshness target, or response-time target is supplied.

Describe the ingestion path, storage and aggregation choices, dashboard query path, and browser update mechanism. Show where delay can accumulate and how you would determine whether the system satisfies the latency requirement. Account for delayed measurements, overloaded ingestion, and a chart that becomes stale.

Clarifying Questions

• Does "latency" mean event-to-screen freshness, chart-query response time, or both, and how will each be measured?
• Which time ranges and label filters must the dashboard support, and how many distinct label combinations can occur?
• Can the display use aggregated points, and how should users see late or missing measurements?
• Should a temporarily disconnected browser catch up on every measurement or fetch the latest chart state?