Traces
Trace Throughput Drop
Updated Jul 29, 2026 · today
Catches a service whose request volume collapsed — crashed, deadlocked, or off the load balancer — when no slow or error spans give it away.
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
Reads span throughput per service, normalized per-minute, and compares the recent rate against the service's own baseline rate (a disjoint older window — no stored baseline). Fires when recent volume falls far below baseline; total silence escalates to critical. A baseline-volume floor keeps low-traffic services from tripping on noise.
Availability
Runs on these tiers:
Want to see this detector firing in the live demo?
Open alerts in the sandbox →Related detectors
- Trace Latency Break
Catches a service whose request latency regressed against its own past — the whole distribution shifted slower.
- Trace Tail Shift
Catches partial degradation: most requests are fine but a slice falls off a cliff — the tail blows up while the median holds.
- Trace Error Origin
Walks the span graph to find the origin service of an error cascade — where the failure started, not the services that merely reported it.
- Trace New Operation
Flags a service serving an operation it never served before — an unannounced deploy, a new endpoint, or a client calling a new path.