Design SLA Tracking Dashboard

Problem Statement: SLA Tracking at Multi-Service Scale

ServiceNow-style SLA dashboards bind contractual uptime to automated credits—not vanity charts.

Define SLI as ratio of good events / valid events in a rolling window—not calendar uptime guesses.

Failure mode to call out early: double-counting downtime when overlapping incidents and flapping probes both write minutes—dedupe keys and merge policy matter more than chart colors.

Problem Statement: SLA Tracking at Multi-Service Scale — design checkpoint (understanding)

Tie every box on the whiteboard to an owner service and a numeric target. Operational note for understanding: track incident write P99, status projection lag, evaluator batch duration, and credit export throughput as first-class SLOs—not generic "enterprise-grade" wording.

When interviewers push on cost, separate hot OLTP path ($) from warehouse analytics ($$) and status CDN egress ($). Credits are rare but legally binding—optimize correctness over microsecond latency there.

Why interviewers care

SLA Tracking Dashboard interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

Interview checkpoint

Name one failure story for Problem Statement: SLA Tracking at Multi-Service Scale that proves you understand real outages, not happy-path diagrams.