AI Gateway logs page lists every request routed

Summary

Observability into multi-provider routing decisions and cost attribution per request eliminates guesswork when debugging why a fallback triggered or which provider handled a request. Token breakdowns across input/output/cache let you optimize expensive modalities.

Why it matters

Observability into multi-provider routing decisions and cost attribution per request eliminates guesswork when debugging why a fallback triggered or which provider handled a request. Token breakdowns across input/output/cache let you optimize expensive modalities.

Sources

1. 1.listing every request your team sends through the gateway, newest first, with cost, token counts, duration, and the model, provider, and region that served it
2. 2.Click any row to open its details next to the list: total cost, a token breakdown across input, output, reasoning, and cache reads and writes, duration, time to first token
3. 3.The fallback path lists every provider attempt for the request in order. Each attempt shows the model, provider, status code, credentials, and how long it took, and failed attempts include the reason, such as a provider timeout or an exhausted routing budget