← Back to the chapter · Previous detail
Technical detail · Time-Series Anomalies: Evaluation and Types
How type errors become alert errors
The wrong anomaly type creates the wrong evaluation problem. A point detector can look good on isolated spikes while missing slow collective drift. A contextual detector can over-alert if context fields are missing or stale. A collective detector can create opaque alerts if it cannot explain which features or windows drove the score. The type label should therefore be part of the alert schema, not just a design note.
Production systems often use a cascade. Edge checks catch impossible values and sensor-health failures. Fog or gateway checks add mode and recent-history context. Cloud or fleet checks score longer windows and cross-device patterns. The cascade only works when each tier reports its evidence and does not overwrite a sensor fault as a process anomaly.
A minimal alert schema needs enough fields to reconstruct the evidence boundary: type, entity, timestamp, window length, baseline id, context version, feature set, sensor-health state, score, threshold, decision, and retest trigger. For a point alert, the window may be one sample and the retest may be immediate. For a contextual alert, the context version matters because a missing shift schedule can turn normal behavior into a false alarm. For a collective alert, the feature set and window are part of the claim, not optional metadata.
The cost of a type error can be estimated before deployment. If 500 assets each produce one false point alert per day, the team receives 500 reviews daily. Requiring a 15-minute collective pattern may cut review load, but it also delays detection and can miss short faults. Conversely, using only a collective detector may hide an impossible single value that should be quarantined at the edge. The production design should state which type is allowed to page humans, which type creates a candidate incident, and which type only updates model health.
Base Rate
Rare true events make false alerts expensive, so review burden matters as much as raw detection count.
Window Length
Collective patterns need enough history, but long windows increase detection latency.
Context Drift
Operating modes and seasonal baselines change, so contextual rules need explicit retest triggers.
Explanation
Operators need the value, context, window, related sensors, and type decision that produced the alert.