LV2 · Toolooo Standard
SLO Incident Burn Simulator
Model request-based error-budget consumption through incident severity, detection, mitigation, recovery and traffic spikes.
Deterministic request-based planning, not monitoring. Minimum hold + additional detection delay + mitigation delay + linear recovery define each incident. Faster detection shortens the modeled incident; real incidents may not follow this assumption.
Google SRE: request-based error budgets and burnWhat this tool does and why
Before you start
What
Model request-based error-budget consumption through incident severity, detection, mitigation, recovery and traffic spikes.
Why
Error rate alone hides how traffic and response delays consume an error budget. A phase model shows which response improvements reduce bad events.
Your Result and Action update in the tool as you change its inputs.
Model note
This browser-side model explains the inputs you choose. Check an important decision against the real system, brief, or production constraints.
Next
How this tool stays honest
How it works
Use deterministic incident presets and editable timings to trace healthy, incident, detection, mitigation and recovery phases. Compare faster response with baseline, inspect repeated incidents and cumulative budget use, and distinguish burn rate from absolute bad-event spending in one evaluation window.
Assumptions
The tool runs in your browser and models the information you provide. It does not know facts outside that model.
Limitations
An educational request-based snapshot, not telemetry or uptime measurement. Healthy errors are zero, recovery is linear and response delays extend incidents. A renewing rolling window is not simulated.
Understand SLO Incident Burn Simulator
What this tool helps you understand
Use deterministic incident presets and editable timings to trace healthy, incident, detection, mitigation and recovery phases. Compare faster response with baseline, inspect repeated incidents and cumulative budget use, and distinguish burn rate from absolute bad-event spending in one evaluation window.
When to use it
When comparing incident detection and recovery timing.
Try a scenario
Keep the request volume and error rate fixed, then shorten detection delay. Compare consumed budget rather than treating the result as uptime telemetry.
How to read the result
Inspect consumed budget and delay costs, then compare faster response. Peak burn is an error-fraction ratio; time to exhaust assumes a fixed remaining budget and sustained incident conditions.
Assumptions and limits
An educational request-based snapshot, not telemetry or uptime measurement. Healthy errors are zero, recovery is linear and response delays extend incidents. A renewing rolling window is not simulated.
Toolooo is part of Khizooology, created byKhizar Imtiaz (khizooo).