Service level objectives
Configure availability or latency targets and error-budget alerts.
A service level objective (SLO) places a target on one monitor and tracks the error budget against it. When the budget is spent too fast, Status raises a burn alert through the monitor's escalation policy. Open Objectives to create and watch objectives.
Define an objective
Select New objective and fill in:
- Name: unique per monitor.
- Measured by: the monitor whose results decide good and bad minutes.
- Indicator: Availability (successful checks) or Latency (successful checks at or below the threshold).
- Target: the percentage to meet, below 100.
- Window: rolling 7, 28, or 30 days.
- Latency threshold: for latency objectives, a check slower than this counts against the budget even when it succeeds.
The editor shows the resulting error budget—for example, how many minutes of bad checks the window allows.
Burn alerts
Burn rate is how fast the error budget is being spent relative to the window. A one-hour burn at 14.4x opens a fast burn event at Critical severity; a six-hour burn at 6x opens a slow burn event at Major severity. Burn alerts enter the same escalation and notification path as incidents—routed by the measured monitor—and resolve when the burn clears.
Read the budget
The Objectives page shows each objective's current SLI, remaining error budget, and daily burn history. Status labels objectives Healthy, Spending fast (under 50% budget), Budget nearly gone (under 20%), or actively burning.