Statistical
Numeric Field Anomaly
Updated Jul 28, 2026 · 1d ago
Discovers the numeric fields your logs carry — payment amounts, cache hit rates, queue depths, inference scores — and flags when one drifts from its baseline.
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
Companion to Golden Signal Monitoring. Where golden signals match known field names (duration_ms, queue_depth), this detector discovers all numeric fields a tenant ships and builds per-field percentile baselines, capped to protect against high-cardinality misconfiguration. Spike thresholds are wider than golden signals since business fields legitimately vary. Overlap with golden signals is skipped to avoid duplicate alerts.
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.
- 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.
- Error Growth Forecast
Spots an error signature whose arrival rate is climbing and projects when it reaches a volume that matters — as a time range, before the incident, not after.