Use Cases
During a sale you need to know which customers lost their basket and why. Filter by one order id and the alert, the trace and the logs all show the same failure.
signal POST /checkout error rate 8.4% · threshold 1%
The path
order_8421 is one failed order. Each screen below is filtered to it, so you never line up timestamps across two tools.
Error rate on POST /checkout crosses its threshold while the rest of the site is healthy. The sale traffic is fine. The payment path is not.
Open one failed order. Three retries sit at the bottom of the waterfall in red, each timing out at exactly 1.75 s, the client's own deadline.
The log lines from those spans share the same trace id. They show the retry budget running out and the connection pool at capacity. The requests timed out waiting for a connection.
outcome
Pool raised and the retry budget cut to two. Checkout error rate back to baseline within one evaluation window.
What it does
One endpoint, one key. Traces, logs, metrics and sessions, linked from the first request.