SLO & Performance
SLO Monitoring
Updated Oct 27, 2026 · today
Error budget tracking with burn rate prediction. Get warned before the SLO breaches, not after.
Example alert
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:
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.
- Browser API Error Rate
Raises warnings when the share of failed browser API calls to a service rises above its baseline.
- Error Session Rate
Raises warnings when the share of sessions with errors or rage-clicks rises above the baseline for that hour and day.
- Page Load Regression
Raises warnings when page-load p95 rises above its service baseline and the good-speed threshold.
- Web Vitals Regression
Raises warnings when a route’s LCP, INP or CLS p75 rises above its baseline and leaves the good range.