Correlate Trace
correlate_traceMatch a trace from one backend to a corresponding trace in another independent backend, using exact trace ID first, then falling back to time-window and service-name overlap heuristics.
Instructions
Try to find the corresponding trace in a second, independently- configured backend (e.g. a Datadog trace and its downstream Sentry error, joined) - given a trace_id known to the primary backend.
Tries a direct trace_id match in the secondary backend first
(confidence "high"); if that fails, falls back to a time-window +
service-name-overlap heuristic search (confidence "low"). This is a
best-effort correlation, not a guaranteed join - see the always-present
limitations in the result for why. Requires a secondary backend to be
configured via SECONDARY_BACKEND_TYPE/SECONDARY_BACKEND_URL (and any
backend-specific fields) environment variables; raises a clear error
otherwise.
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": "correlate_trace"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| trace_id | Yes | Trace identifier, as known to the primary (already configured) backend. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| matches | Yes | ||
| limitations | Yes | ||
| primary_trace_id | Yes |