Core concepts
A burn rate of 1.0 means you are exactly on track to use the full budget by
the end of the window. A burn rate of 14.4 means you will exhaust the monthly
budget in about 50 hours (a 30-day window) if the current rate continues.
Alerting
Burn-rate alerting is live. Create a rule in Settings → Alerts, set a threshold, and breaches are delivered to a webhook you control — Slack, Discord, or any HTTPS endpoint. Alongside burn rate you can alert on error rate, p95 latency, gateway overhead p99, spend, and quota used. Alerting is available on paid plans. Per-SLO configuration (custom SLIs, targets, windows) is not built — the dashboard tracks the burn rate against a default availability target, and the target is per plan, not per SLO.Dashboard
The/slo page in the dashboard shows:
- Error budget remaining — percentage and absolute count against the availability target.
- Burn rate — how fast the error budget is being consumed relative to the window.
- Per (provider, model) latency — p50 / p95 / p99 and error rate from the hourly rollups.
- Top failing requests — the traces that contributed most to budget burn, linked directly to the trace viewer.
API
apps/web/app/slo/budget.ts); there is no per-SLO objective field.
Related
- Architecture — performance budgets
- Predictive guardrails
- API reference