Cross-service Search

A single request crosses many services. When you only have a traceID, an orderID, or an error string, search ties the pieces back into one path.

Open a Search tab (⌕) from the sidebar or by searching a project.

Search

Enter a traceID, orderID, or error keyword. Results show across the project, with a hit count (shown / total) and the services that matched.

Narrow the result set with the filters:

All / Errors / Warnings
Last 24h

Step through results with previous / next hit, or click a hit directly. Use load more to pull earlier or newer hits.

Trace Context

Select a hit to open Trace context on the right — this is the point of search.

Cross-service path — the ordered path of this request as it moved across services.
Nearby signals — related log lines around the selected hit.
Service, trace, level, and time of the selected hit.
Open live jumps to the live stream at that point.
Copy takes the whole trace context out.

Hand It To The Agent

The cross-service path you copy here is one of the cleanest artifacts you can give an agent: the full route of one request, in order, with the failing hop visible. Pair it with evidence pins from Log investigation techniques and the agent has both the path and the annotated lines.