Statistical
Error Rate Anomaly
Updated Jul 28, 2026 · 1d ago
Per-service error percentage anomalies vs baseline, with sustained-elevation guards so a single noisy minute doesn't fire and slow ramps still get caught.
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
Computes error-to-total ratio per service per minute and compares against a rolling baseline. A dual-gate (sample count + temporal coverage) prevents false alarms during low-traffic periods and ramp-up. Learning period: 5 days.
Availability
Runs on these tiers:
Want to see this detector firing in the live demo?
Open alerts in the sandbox →Related detectors
- Volume Anomaly
Detects spikes, drops, and flatlines in log volume vs daily and weekly baselines per service.
- Silence Detection
Catches services that stop logging when they normally log every N seconds. The most dangerous failure mode: no errors, just absence.
- Outlier Detection
Multi-dimensional outliers in log feature space. Catches subtle anomalies that single-axis thresholds miss.
- Numeric Field Anomaly
Discovers the numeric fields your logs carry — payment amounts, cache hit rates, queue depths, inference scores — and flags when one drifts from its baseline.
- Post-Change Regression
Checks whether a deploy, config change or scale event actually made things worse, by comparing the window after the change against the matched window before it — per service.