SLOs & error budgets
Know how much error you can afford before users complain
Each catalog service gets an indicator (SLI), an objective and an error budget. The SLI is the ratio of good events to the total in the window, excluding maintenance intervals; budget spent and burn rate come from formulas shown on screen.
Next to the SLO, the screen shows recent changes to the same service, deployments and flag changes, to connect budget consumption to what changed.
How it works
- Error budget = 1 − objective; budget spent = (1 − SLI) ÷ (1 − objective).
- Multi-window alerting: it only fires when both the long and the short window cross the threshold, which avoids alarms from isolated spikes.
- Fast burn: 1 hour and 5 minutes above 14.4. Slow burn: 6 hours and 30 minutes above 6.
- Composite SLOs with weights, per-SLO annotations and an audited error budget reset with a required reason. An exhausted budget can block the promotion of a release through the delivery policy.
- A burn rate alert marks the service component as degraded on the status page.
- Read access through API v1 and the MCP server, with SLI, budget and burn rates.
Base: https://aiuby.com/api/v1
GET /engineering/slos # workspace SLOs (objective as a percentage)
GET /engineering/slos/{id} # SLO state; read-only: does not record alertsWhat it does not do
- The API and MCP are read-only: workspace admins create and change SLOs in the UI.
- Native collection only from Prometheus, through a scheduled query to a public HTTPS URL; other tools send samples through the API.
- Up to 100 SLOs per workspace.