multi-router.aidocs

Observability

Request Logging

What each router records about its requests, and the Storage Policy that caps it.

Request logging is the setting on each router that decides what Multi-Router records about the router's requests. It has two parts: request metadata, which is the request record shown in Traffic, and payloads, which are the full request and response. An administrator's Storage Policy sets the most any router can record, and each router records at or below that level. A router that has no setting of its own follows the Storage Policy.

Request metadata

Request metadata is the request record shown in Traffic. The Request Metadata setting has these levels:

LevelDashboard descriptionRecords
Full MetadataComplete request metadata is logged.Every field of every request.
Anonymous MetadataAll request metadata except user-identifying fields are logged.Every request, with the customer id, session id and peer IP left empty.
Failures onlyOnly failed requests are logged.Requests that returned a status of 400 or above, or recorded an error during the response.
NoneRequest logging for this router is disabled.No records. Traffic and its stats leave out the router's requests.

Budget enforcement counts every request whatever the router logs. The spend shown on the Budgets pages comes from request records, so it includes a router's requests when the router records them. Anonymous Metadata suits routers that serve end users, keeping usage, latency and cost complete while leaving the identifying fields empty; payloads, when stored, hold the request as sent, including any customer id in its body.

Payloads

The Request and Response Payloads setting decides which requests have their full request and response stored:

LevelStores
All PayloadsEvery request and response.
SampleA chosen percentage of requests, up to the administrator's limit.
Failures onlyRequests that returned a status of 400 or above.
NonePayload storage off.

Payloads depend on metadata: with metadata at None, payload storage is off, and with metadata at Failures only, payloads are stored for failures at most. Sampling picks requests by their request id, so each request's place in the sample is fixed, and the share matches the percentage over many requests.

Setting it in the dashboard

Back to Routers

Support bot

enabledstatic
productionsupportAdd tag

Answers customer questions in the help center chat widget.

rt_9Hk3Ws7PzQ·created Mar 4, 2026·updated Sep 30, 2026
Disable
OverviewTrafficActivity

Aliases

Model

Prompt

Request Logging

What this router records about its requests. Capped by the administrator's Storage Policy.

Request Metadata
NoneRequest logging for this router is disabled.Failures onlyOnly failed requests are logged.Anonymous MetadataAll request metadata except user-identifying fields are logged.Full MetadataComplete request metadata is logged.
Request and Response Payloads
NoneRequest payload logging is disabled.Failures onlyRequest payloads are logged for failed requests only.SampleRequest payloads are logged for a sample of requests only.
Log10% of requests (up to the administrator limit of 10%).
All PayloadsAdministrator managedRequest payloads are logged for all requests.
Unsaved changesCancel Save

Settings

Per-router configuration. Persisted in the router's versioned config blob.

Editing a router's Request Logging: Anonymous Metadata with a 10% payload sample, and All Payloads above the administrator's limit. Select to enlarge.

The Request Logging panel on a router's page shows the current Request metadata and Request payloads. Edit opens both settings; levels above the administrator's Storage Policy are shown as Administrator managed and stay unselected. For a fallback or weighted router, logging follows each member router, and the panel says so; set logging on the members. See Router Settings.

Through the API, the levels are observability.metadata_level with the values full, anonymous, failures_only and none, and observability.request_capture with the values all, sample, error_only and none, with the sample share in observability.payload_sample_pct. Both settings also take inherit, the default, which follows the Storage Policy:

Anonymous metadata and a 10% payload samplebash
curl -X PATCH https://api.multi-router.ai/v1/routers/rt_9Hk3Ws7PzQ \
  -H "Authorization: Bearer $MR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "observability": { "metadata_level": "anonymous", "request_capture": "sample", "payload_sample_pct": 10 } }'

Storage Policy

The Storage Policy is the administrator setting that caps what every router in the installation can record. Its traffic logging switch turns request records on or off for every router, and its mode sets the cap:

ModeMost a router can record
Anonymous request metadata (usage only)Anonymous Metadata, with payload storage off. This is the default.
All request metadataFull Metadata, with payload storage off.
Store everythingFull Metadata and payloads, up to the administrator's payload capture level and sample percentage.

With the default mode, Traffic holds usage, latency and cost for every request with the customer id, session id and peer IP left empty, and holds usage figures only.

How payloads are protected

Payloads are stored encrypted, separately for each organization, and are read only through the organization's own Traffic page. Before storage, credential headers, which are Authorization, x-api-key, X-MR-Api-Token, anthropic-api-key, cookie, set-cookie and any header whose name contains token, key, secret, password or auth, are replaced with [redacted]. A body larger than 32 MiB is stored up to that size and marked truncated.

Fields by level

The levels differ in which fields they keep:

FieldFull MetadataAnonymous Metadata
Routing, model, provider, regionKeptKept
Tokens, cost, latency, status, errorsKeptKept
API key idKeptKept
Correlation idKeptKept
Customer id (user or metadata.user_id)KeptEmpty
Session idKeptEmpty
Peer IPKeptEmpty
Request DetailCost
Was this helpful?