Get one distributed trace
get_traceOne trace (app → backend → dependencies) as a tree: names, services, start offsets, durations, HTTP status and errors, plus the error events linked to it. Take the trace_id from an event or from search_traces. Use it to see where the time went or what failed first. Long traces page with next_cursor.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"trace_id": "<trace_id>"
},
"name": "get_trace"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Spans (default 100) | |
| cursor | No | next_cursor from the last answer | |
| trace_id | Yes | 32-character hex W3C trace id |