Key capabilities
- Support availability, latency-threshold and time-slice SLIs
- Show allowed failures, budget consumption and burn-rate math
- Simulate incident duration, error rate and traffic impact
- Generate Prometheus rules, OpenSLO YAML and reports
SLO & Error Budget Studio
Model availability, latency or time-slice SLIs, calculate burn rates, import observations, simulate incidents, and draft Prometheus and OpenSLO output.
SLO data and queries are calculated only in this browser
Service names, metric queries, CSV rows and filenames never enter anonymous analytics. No monitoring platform is contacted.
SLO model
CSV is limited to 5 MiB and 20,000 rows. Objective windows support 1–366 days.
1
Objective definition
%
2
Observed data
/min
3
Incident simulation
min
%
4
PromQL
Use the $window placeholder. Generated rules are drafts and must be validated in the target Prometheus.
Enter an objective or load the sample
Budget consumption, trends, incident impact, multi-window alerts and an OpenSLO draft will appear here.
Results are deterministic estimates from the supplied data, not a substitute for real traffic, sampling, late data, maintenance windows or organizational budget policy.
About SLO & Error Budget Studio
Calculate budgets, simulate incidents, and draft alerts and OpenSLO. Model availability, latency or time-slice SLIs, calculate burn rates, import observations, simulate incidents, and draft Prometheus and OpenSLO output. The core workflow is designed to run in your current browser.
Useful for
- Review whether a target matches traffic and failure tolerance
- Estimate an incident’s impact on the remaining error budget
- Prepare multi-window burn alerts and a vendor-neutral SLO draft
Frequently asked questions
Is SLO & Error Budget Studio free to use online?
Yes. SLO & Error Budget Studio opens in a modern browser and does not require desktop software installation.
What is SLO & Error Budget Studio useful for?
Common use cases include Review whether a target matches traffic and failure tolerance; Estimate an incident’s impact on the remaining error budget.
Is my input or file uploaded?
The core processing workflow is designed to run locally in the browser. Key capabilities include Support availability, latency-threshold and time-slice SLIs, Show allowed failures, budget consumption and burn-rate math, Simulate incident duration, error rate and traffic impact; account, comments, and anonymous analytics may still create normal site requests.
Comments
0 comments
AAccount
Sign in to comment and reply.
No comments yet. Be the first to leave feedback.