SLO & Performance
SLO Monitoring
Updated May 31, 2026 · today
Error budget tracking with burn rate prediction. Get warned before the SLO breaches, not after.
Example alert
checkout-service SLO: 14-day error budget at 87% burn, projected to exhaust in 36h
Exact wording varies — the detector generates titles from the anomaly it finds. This is representative of what an alert looks like when it fires.
How it works
Implements the Google SRE multi-window burn rate algorithm. Short window (5 min) + long window (1 hour) must both exceed thresholds before firing, reducing false alarms from transient spikes. You define the SLO target; Epok tracks the budget.
Availability
Runs on these tiers:
trialteamgrowthenterprise
Want to see this detector firing in the live demo?
Open alerts in the sandbox →Related detectors
- Golden Signal Monitoring
Latency, saturation, and per-service error rate. Three of the four SRE golden signals — traffic is covered by Volume Anomaly.