multi-router.aidocs

Observability

Request Detail

Every field of a single request, its errors, and its stored payloads.

Request detail is the full record of one request, opened by selecting its request id in Traffic. The header shows the request id, status, model and provider, and a row of tiles gives the Latency, Cost, Tokens, time to first token, Attempts and Router overhead. Sections below give every recorded field, and when the router stored payloads, Full Request Payload opens the request and response themselves.

Request

Engineering · org_7Tq2Wd9KxP

Overview · Traffic

CustomizeSave view
Time:
1h24h7d30d
CustomFilters
Search any id (request/correlation/session)…
Export
Requests
128,403
Success rate
99.4%
5xx errors
142
Tokens
84.2M
Latency · p95
1,240ms
Latency · p99
3,180ms
Cost
$1,284.50
Customers
312
Requests · Count / time128,403
Outcome · 5xx / time142
Latency · p95 / time1,240ms
Cost · Total / time$1,284.50
Requests
Page 125 / page
Columns
DateTimeRequest IDRouterAliasModelVendorIn/OutCostLatencyStatus
2026-09-3014:32:11req_Lw4Tn8Vb2ksupport-bot—anthropic/claude-sonnet-4.5anthropic2,310/512$0.011.94s200
2026-09-3014:32:09req_9Pc1RmYe4srt_9Hk3Ws7PzQ—anthropic/claude-haiku-4.5bedrock860/210$0.0021640ms200
2026-09-3014:32:07req_8Fq2LmXo1crt_9Hk3Ws7PzQ—anthropic/claude-haiku-4.5bedrock1,240/380$0.0035808ms200
req_8Fq2LmXo1c200anthropic/claude-haiku-4.5bedrock
Full Request Payload →
Latency
808ms
Cost
$0.0035
Tokens
1,240 → 380
TTFT
402ms
Attempts
1
Router overhead
1.2ms
Request
Request ID
req_8Fq2LmXo1c
Timestamp
14:32:07
Organization
org_7Tq2Wd9KxP
Token
tok_4Rf8zLm2Qa
Correlation ID
order-4411
Customer
—
Session
—
Peer IP
203.0.113.24
Routing
Alias
—
Router ID
rt_9Hk3Ws7PzQ
Model requested
anthropic/claude-haiku-4.5
Model served
anthropic/claude-haiku-4.5
Vendor
bedrock
Variant
geo
Region
us-east-1
Wire id
us.anthropic.claude-haiku-4-5-20251001-v1:0
Prompt binding
Prompt ID
—
File path
—
Revision
—
Latency
Total
808ms
TTFT
402ms
Request upload
180µs
Router overhead
1.2ms
Upstream
806ms
Router response
240µs
Tokens
Prompt
1,240
Completion
380
Request bytes
6,412
Response bytes
2,186
Cost
Total
$0.0035
Input
$0.0014
Output
$0.0021
Cache read
$0
Cache write
$0
Provider response
Request upload
180µs
Router · overhead
1.2ms
Upstream200
806ms
Router · response
240µs
Total 807.6ms
2026-09-3014:32:04req_3Zr6KdWq8nclaude-code-eng—anthropic/claude-sonnet-4.5vertex5,120/1,034$0.033.21s200
2026-09-3014:31:58req_6Ym2HcPa5tsupport-bot—anthropic/claude-sonnet-4.5anthropic0/0$0212ms429
A request opened in Traffic: the summary tiles, the Request, Routing, Prompt binding, Latency, Tokens and Cost sections, and the latency breakdown. Select to enlarge.

The Request section identifies the request and its caller:

FieldShows
Request IDThe request id, such as req_7Kd2Qx9WmB4Tn6Ls, also returned in x-mr-request-id.
TimestampWhen the request arrived.
OrganizationThe organization id.
TokenThe id of the API key that made the request, such as tok_4Gm8Rq2VxN.
Subject typeThe kind of Machine Identity workload, when one made the request.
Machine issuerThe identity provider of the workload.
Machine subjectThe workload identity.
Machine bindingThe machine binding the workload matched.
Correlation IDThe caller's x-mr-correlation-id.
CustomerThe caller's customer id.
FeatureThe caller's feature label from X-MR-Feature-Id, such as support/triage.
SessionThe caller's session id.
Peer IPThe address the request came from.

Routing

The Routing section shows how the request was served:

FieldShows
AliasThe alias the request used, linked to the router.
Router IDThe router that served the request, linked to its page. For a fallback or weighted router, this is the member that served it.
Model requestedThe model named in the request.
Model servedThe catalog model that answered, such as anthropic/claude-sonnet-4.5.
VendorThe provider that served the request.
VariantThe offering variant, such as standard or geo.
RegionThe region that served the request.
Wire idThe provider's own model id, such as claude-sonnet-4-5-20250929.

Prompt binding

The Prompt binding section shows the bound prompt the router applied, with dashes when it applied none. It shows the Prompt ID, File path and Revision used; for a GitHub prompt it also shows the Repository, and the revision is the commit, linked to the file at that commit on GitHub. See Prompt Binding.

Latency

The Latency section splits the request's total time into its parts, and the Provider response chart shows the same parts as a timeline:

FieldMeasures
TotalFrom the request arriving to the response finishing.
TTFTTime to first token: from the request arriving to the first streamed output.
Request uploadReceiving the request body from the caller.
Router overheadMulti-Router preparing the request before sending it to the provider.
UpstreamThe provider handling the request.
Router responseMulti-Router finishing the response after the provider.

Tokens

The Tokens section shows Prompt tokens, with how many were read from the provider's prompt cache and how many were written to it, by cache lifetime, and Completion tokens. It also shows the request and response sizes in bytes.

Cost

The Cost section shows the Total and its parts: Input, Output, Cache read and Cache write, by cache lifetime, and Web search and File search when the request used those tools. See Cost.

Errors

A failed request shows an error card with its category, a readable description and hint, the provider's status code when the provider answered, the error kind and the error message. The categories are Request error, Config error, Upstream error and Other error. Requests refused by Multi-Router's per-key rate limit or by a budget are answered before a record is written, so they appear in the caller's logs and not in Traffic. The error kinds recorded are:

Error kindLabelMeaning
invalid_requestInvalid requestThe request was malformed, or Multi-Router refused it before sending, such as for a model the router does not serve.
auth_errorAuthentication errorThe provider refused the credential.
model_not_foundModel not foundThe provider reported that the requested model is not available.
config_errorConfiguration errorThe router is set up in a way that cannot serve the request, such as a missing provider key.
rate_limit_errorRate limitedThe provider's rate limit was reached.
timeoutTimeoutThe provider took too long to respond.
upstream_errorUpstream errorThe provider returned an error.
cancelledCancelledThe request was cancelled before it finished.
client_disconnectclient_disconnectThe caller closed the connection before the response finished.
metering_failedmetering_failedThe response finished, and its token usage could not be read.
internal_errorinternal_errorMulti-Router hit an internal error while serving the request.

Payloads

Payloads are the full request and response, stored when the router's Request Logging settings capture them. Full Request Payload in the detail header opens them; a newly finished request shows Full Request Payload available in a few minutes, with a countdown, while its payload is being stored. The payload viewer shows:

PartContents
Client requestThe request exactly as the caller sent it.
Provider RequestThe request as Multi-Router sent it to the provider, with any bound prompt applied. Shown when it differs from the client request.
ResponseThe response returned to the caller.

Each part opens as a tree or as raw text, Split view shows two parts side by side, and Headers shows the headers of each part, with credentials such as Authorization replaced by [redacted]. Copy copies a body, and a badge marks a body that was decompressed or truncated. See Request Logging.

TrafficRequest Logging
Was this helpful?