Traces
Trace New Operation
Updated Jul 28, 2026 · 1d ago
Flags a service serving an operation it never served before — an unannounced deploy, a new endpoint, or a client calling a new path.
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 spans and compares each (service, operation) pair in the recent window against the set seen in a disjoint baseline window. A pair that recurs now but was absent before is a new code path. Two guards keep it honest: the baseline must carry enough total spans, and the new operation must recur (not a one-off span).
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 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.