← Back to the chapter · Previous detail · Next detail →

Technical detail · Time-Series Anomalies: Evaluation and Types

Preserve the alert evaluation record

Evaluation record for one alert
alert_id: pump-17-2026-07-03T10:20Z
detector: residual-ewma-v4
window: 10:15:00 to 10:20:00 event time
score: 4.8 sigma-equivalent residual
threshold: 4.0
data state: complete window, no imputed samples
operator label: true positive
incident id: pump-17-bearing-review-042
detection latency: 3 min after first threshold crossing
review latency: 14 min after alert routing

This record supports precision, recall, F1, false-alert workload,
time-to-detection, and post-incident audit without changing the detector.

Worked example: if pump-17 raises four overlapping alerts between 10:17 and 10:20 for the same bearing review, the metric job should keep one incident id, one first-alert time, and the duplicate count. Precision then scores one reviewed true positive instead of four, while workload reporting can still show that the operator saw four routed notifications.

← Back to the chapter · Previous detail · Next detail →