All screens
42 days

Alert SLA Targets

Each alert severity tier carries a service-level objective: a ceiling on time-to-acknowledge, a ceiling on time-to-resolve, and a floor on the share of alerts that met both. Targets are shown against an illustrative trailing-window actual. A tier's headline verdict is the worst of its three signals — one breaching clock turns the whole tier red.

4 tiersBreaching2Meeting2

Targets vs Actuals by Severity

Time clocks compare an actual against its target ceiling; attainment compares against a floor. The pill on each row is that signal's traffic light.

Critical12 alerts

User-facing outage or a frozen LIVE event-day transition.

Breaching
Time to acknowledge
target 5m9mBreaching
Time to resolve
target 30m41mBreaching
Attainment (met both)
target 99%91%Breaching
High34 alerts

Degraded core flow or a stalled item past its second escalation rung.

Breaching
Time to acknowledge
target 15m16mBreaching
Time to resolve
target 2h2.0hAt Risk
Attainment (met both)
target 97%95%Breaching
Moderate71 alerts

Non-blocking regression or a budget nearing its threshold.

Meeting
Time to acknowledge
target 1h38mMeeting
Time to resolve
target 8h6.7hMeeting
Attainment (met both)
target 95%97%Meeting
Low58 alerts

Informational signal or a deferred cleanup item.

Meeting
Time to acknowledge
target 4h1.6hMeeting
Time to resolve
target 2d1.1dMeeting
Attainment (met both)
target 90%98%Meeting

SLA targets and actuals are illustrative cockpit project-tracking state authored in src/data/sla, not product data. Lower-is-better clocks breach when the actual exceeds the target; the attainment floor breaches when the actual falls below it.