AI Gateway logs now have a dedicated page
AI Gateway’s dedicated logs expose per-request cost, tokens, latency, routing, and provider fallbacks, making agent failures and spend anomalies easier to trace.
The new **Logs page** lists gateway requests with cost, token counts, duration, model, provider, and region. Request details include time to first token, cache and reasoning tokens, policy flags, and the ordered fallback path.
Use filters and request-ID search to debug agent failures or compare routing behavior. Filtered views are shareable by URL and exportable as **CSV or JSON**, which makes targeted cost and reliability analysis easier.
The new **Logs page** lists gateway requests with cost, token counts, duration, model, provider, and region. Request details include time to first token, cache and reasoning tokens, policy flags, and the ordered fallback path. Use filters and request-ID search to debug agent failures or compare routing behavior. Filtered views are shareable by URL and exportable as **CSV or JSON**, which makes targeted cost and reliability analysis easier. The page records what happened but does not define alerts, retention, or automated remediation. Diagnosis still requires interpreting provider failures, routing-budget exhaustion, and latency in the context of the agent run.
This turns gateway observability into a request-level diagnostic surface: teams can inspect routing, fallbacks, latency, tokens, policy flags, and cost together, then export or share the evidence. It complements controls and serving options in the prior candidates, but does not close the operational loop because alerting, retention, interpretation, and remediation remain outside the page.