Observability
Request Tracing
Request, session, correlation and customer ids, and the response headers that describe how a request was served.
Request tracing ties a request in Multi-Router to the caller's own systems. Every response carries the request's id, and callers can attach their own ids, for a conversation, a job or an end customer, which Traffic records, filters and searches. Response headers also report how the request was served, such as the provider and the number of attempts, so an application can log them with its own records.
Ids
An id is a value that names a request, or a group of requests, in Traffic. A request carries these ids:
| Id | Set by | Sent as | Use |
|---|---|---|---|
| Request id | Multi-Router | Returned in x-mr-request-id | Finds one request in Traffic. |
| Session id | The caller | x-mr-session-id request header | Groups the requests of one conversation or agent session. |
| Correlation id | The caller | x-mr-correlation-id request header, returned in the response | Matches a request to an entry in the caller's own logs. |
| Customer id | The caller | The user field on Chat Completions, or metadata.user_id on Messages | Attributes usage to the caller's end customer or tenant. |
Traffic records the first 200 characters of a session or correlation id and matches them exactly, and the response returns the correlation id in full. Claude Code sends its own session id, which Traffic records when no x-mr-session-id is sent. With Anonymous Metadata, the router leaves the session id and customer id empty. See Request Logging.
Response headers
Response headers describe how Multi-Router served a request. Every response carries x-mr-request-id, and x-mr-correlation-id when one was sent. Successful responses from Chat Completions and Messages also carry the rest:
| Header | Value |
|---|---|
x-mr-request-id | The request id, on every response including errors. |
x-mr-correlation-id | The caller's correlation id, when one was sent. |
x-mr-provider | The provider that served the request. |
x-mr-upstream-model | The catalog model that served the request. |
x-mr-upstream-wire-id | The provider's own model id. |
x-mr-region | The region that served the request, when known. |
x-mr-attempts | How many attempts the request took. |
x-mr-composer | The fallback or weighted router, when one handled the request. |
x-mr-policy | How the router was chosen. The values are in the next table. |
x-mr-model-deprecated | true when the model served is deprecated. |
x-mr-model-replaced-by | The model that replaces a deprecated model. |
| x-mr-policy | The router was chosen by |
|---|---|
static | A router id in the model field. |
model_alias | A built-in model alias in the model field, such as claude-haiku-4-5. |
header | The X-MR-Router header. |
fallback | A fallback router. |
weighted | A weighted router. |
passthrough | A provider and model name in the model field, such as anthropic/claude-sonnet-4.5. |
bare | A model name on its own in the model field. |
Claude Proxy responses also carry x-mr-upstream-wire-id, and Claude Proxy, Codex Proxy and Gemini Proxy responses pass the provider's own headers through. Adaptive Router responses carry x-mr-rule, the id of the rule that planned the request.
Finding a request
To find a request from an application log:
- Log the
x-mr-request-idresponse header, or send anx-mr-correlation-idwith each request. - In Traffic, paste the id into the search box, with a time range that covers the request.
- Select the request id to open its detail. See Request Detail.
A session id finds every request of a conversation the same way, and the Customers view and the Customer filter show usage for one end customer.