Traces
Trace Latency Break
Updated Jul 28, 2026 · 1d ago
Catches a service whose request latency regressed against its own past — the whole distribution shifted slower.
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 request spans and compares each service's recent p95 duration against its own baseline window (the older slice of a longer lookback — no stored baseline). Fires when recent p95 is ≥3× baseline with enough requests in both windows to trust the quantiles. Severity is floored by absolute latency so a multiple on a still-fast tail doesn't page.
Availability
Runs on these tiers:
Want to see this detector firing in the live demo?
Open alerts in the sandbox →Related detectors
- 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 Throughput Drop
Catches a service whose request volume collapsed — crashed, deadlocked, or off the load balancer — when no slow or error spans give it away.
- 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.