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 makes gateway behavior inspectable at request level by joining cost, latency, token, policy, provider, and fallback evidence in one exportable surface. It supports debugging and routing comparisons, but confirms that observability alone does not close the loop: teams still need alerts, retention choices, run-level interpretation, and remediation outside the page.