- Open SLOsGo to Reports and open the SLOs tab.
- Create an SLOChoose "New SLO", enter a Name and pick the Monitor.
- Pick the kindChoose Availability (share of time up) or Latency (share of checks faster than a threshold).
- Set target and windowEnter the Target (%), for example 99.9, choose a Threshold for latency, and a Rolling window of 7, 14, 28 or 30 days.
- SaveChoose "Save SLO". The table shows attainment, error budget and burn rate.
A service level objective (SLO) says how reliable a monitor should be over a rolling window, for example "99.9% available over 30 days". The error budget is the downtime, or the number of slow checks, that the objective still allows. SLOs are a Team plan feature.
Create an SLO
- Go to Reports and open the SLOs tab.
- Choose New SLO. The button is disabled until the workspace has at least one monitor.
- Enter a Name, such as "Checkout API availability", and choose the Monitor.
- Pick the Kind:
- Availability — share of time the monitor is up.
- Latency — share of checks faster than a threshold. Choose the Threshold, from 50 ms to 30 s; checks at or under it count as good.
- Enter the Target (%), between 0 and 100 (exclusive), for example
99.9. - Choose the Rolling window: 7, 14, 28 or 30 days.
- Choose Save SLO.
Read the table
- Attained: the share of good time (availability) or fast checks (latency) in the window so far.
- Error budget: how much of the allowance is left, with a bar and "used X of Y". The badge reads Within budget, Budget running low (under 25% left), Error budget exhausted (the objective is already missed for this window) or Insufficient data.
- Burn rate (1 h / 6 h): how fast the budget is being used compared with an even pace. 1 means the budget would be used up exactly at the end of the window; 2 means twice as fast; 0 means nothing was used. The 1-hour rate reacts quickly, the 6-hour rate shows whether a problem is sustained.
- Coverage: the share of the window that has check results.
A useful rule of thumb: a 99.9% availability objective over 30 days allows about 43 minutes of downtime; 99.5% allows about 3.6 hours.
How SLOs are calculated
- Planned maintenance does not count against availability objectives.
- Below 95% measurement coverage, attainment is not claimed and the SLO shows Insufficient data rather than a guess. New monitors and monitors with long pauses show this until enough data exists.
- SLOs do not send alerts. Check the SLOs tab, or keep alerting on the monitor itself.
Edit or delete
Use Edit or Delete in the table. Deleting stops the error budget tracking; the monitor and its data are kept. If the workspace leaves the Team plan, existing SLOs stay listed but cannot be edited or created.
Frequently asked questions
Which plan includes SLOs?
The Team plan, including the Team trial.
Does maintenance use up my error budget?
No. Time inside maintenance windows is excluded from availability objectives.
Why does my SLO say insufficient data?
Less than 95% of the window has check results, for example because the monitor is new or was paused. Attainment is shown once coverage is high enough.
Can an SLO alert me when the budget runs low?
Not currently. SLOs are shown on the SLOs tab under Reports and do not send notifications.
