Try it
Try to break this SLO.
Push the error rate up and watch the error budget burn. SteadyNines spots the burn, finds the cause and asks you to approve the fix before the SLO breaks.
- Burn rate
- 0.8×
- Budget left
- 71%
- Time to exhaustion
- 26.5 days
- Status
- Example run
Simulated service and data. One second here is about six hours of a real 30-day SLO window.
In this simulation card-auth-api has a 99.9% availability SLO over 30 days, so 0.1% errors is the allowed rate. Pushing the error rate above that burns the error budget: at 1.44% errors the burn rate is 14.4× and the budget would be gone in about two days; at 3.6% it is 36× and gone in 20 hours. Once the burn has run at 6× or more for an hour, SteadyNines opens a situation, names deploy #4821 (issuer retries) as the likely cause and proposes rolling back to #4820. Approving the rollback stops the burn with most of the budget left. A slow leak between 1× and 6× becomes a ticket with a fix drafted for the AI Engineer instead. Doing nothing breaches the SLO, which is where most tools start.
Now try it on your SLOs.
Start with one SLO. See the loop work in your estate in two weeks.