Observability: Find the request. See what happened.

Request logging does not capture prompt or response bodies. Log rows record structured routing, timing, token, status, and billing metadata correlated by x-nr-request-id. Metadata-only does not mean personal-data-free: custom attribution tags (x-nr-tags and nrouter_tags, which are stripped before provider dispatch) and end-user identifiers passed in user are stored with the log record if you send them. Separately, if you enable response caching, cached entries store the response body—which can include echoed prompt content—for the cache TTL.

A request trace records gateway step timings—such as authentication, guardrail checks, routing selection, credit reservation, upstream wait time, and settlement—on authenticated requests. It does not provide visibility inside an upstream provider’s internal model execution or your surrounding application code, and requests refused before authentication cannot produce a tenant log row. Trace depth follows your organization trace setting (and can be lowered per call with x-nr-trace), and the recorder explicitly marks coverage as truncated or unfinished if a trace reaches its event cap.

On buffered requests, settlement runs before headers return, so priced responses carry the settled USD amount in x-nr-request-cost with x-nr-cost-status: exact. On streaming requests, response headers are sent before the first token arrives, when final token usage does not exist yet; initial stream headers report x-nr-cost-status: unpriced, and the settled cost is written to the request log row after the stream completes. If a request’s price cannot be determined, cost status remains unpriced rather than reporting $0.

Request logging is part of gateway settlement, not a zero-latency background step. On buffered text calls, the gateway records the settled spend row and discharges the credit hold before returning response headers to the caller. On streaming calls, headers and tokens stream first and settlement is recorded when the stream finishes.

Pay as you go is the standard self-serve plan and retains searchable request logs and traces for 7 days. Longer retention windows (up to 30 days) apply only to custom enterprise agreements and grandfathered legacy subscriptions, which are no longer sold. Organization audit logs are retained for 18 months. Request logs, trace inspection, and CSV export are included on pay as you go, while trace depth is governed by your organization settings and SIEM audit streaming is reserved for enterprise agreements.

You can filter request logs in the dashboard and export them as CSV at any time, and your application can record the x-nr-request-id, x-nr-model, x-nr-latency-ms, and x-nr-request-cost response headers directly in your own telemetry. In the dashboard, saving a destination and sending a test event only verifies that the address is reachable; automatic log delivery is not available as a live customer guarantee, so use CSV export and response headers for external analysis.