observe
api unreachable
The research API did not answer, so observations cannot be listed. Nothing is shown in its place — an empty list is correct here, invented rows are not. What observations would look like is below.
503 Service Unavailable
what this page shows
- —every anomaly a detector flagged, with the measurement and the baseline it fired against
- —each one records the thresholds used, so it stays interpretable after those thresholds change
- —the pipeline is deterministic — no model decides what counts as an anomaly
token
DEMOTOKENxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
detector
volume-acceleration-v1
measured
volume 4.2× its window median
baseline
median of the preceding 3h, 11 readings
thresholds used
volume_ratio 3.0 · saturation 12.0
novelty
0.62
An anomaly records the thresholds it fired on, so it stays interpretable after those thresholds change. Nothing here involves a model: the pipeline is deterministic, and the expensive layer only ever sees what these cheap functions already flagged.