All articlesLLM Proxy
Read an LLM trace
Understand provider, token, latency, cost, policy, and refusal details for a model call.
A trace explains a model call
A trace keeps the operational record for one model interaction. Use it to answer who made the request, which provider handled it, what it cost, whether policy allowed it, and what audit evidence is available for review.
Trace fields to inspect
Start with the agent and team that initiated the request, then review the provider, model, latency, token count, and cost. The route or fallback selected by LLM Proxy explains why the request took that path.
The most important fields for governance are the policy decision, any blocked or redacted content, and the correlation IDs that connect the trace to audit reporting or support evidence.