concept

Agent tracing

Agent tracing captures the full execution graph of an agent run — every step, every tool call, every model output — so engineers can debug, audit, and improve the agent over time.

Production agents in 2026 are impossible to debug without tracing. Each agent run emits a structured trace: planner step, tool calls + arguments + results, model outputs at each step, latency per stage, total token spend, final outcome. Tools that ship tracing: Langfuse, Braintrust, Phoenix (Arize), LangSmith, OpenLLMetry. Best practice: trace 100% of production runs but sample for evals; pin prompt version IDs to traces; alert when failure rate or token budget spikes. Tracing turns agents from black boxes into observable systems.

When to use agent tracing

Common mistakes

FAQ

What is agent tracing?

Agent tracing captures the full execution graph of an agent run — every step, every tool call, every model output — so engineers can debug, audit, and improve the agent over time.

When should I use agent tracing?

Any production agent. Multi-step LLM pipelines.

What are the most common mistakes with agent tracing?

Tracing only failures — you need success samples to know what good looks like. No version pinning in traces — can't attribute regressions to prompt changes.

Last updated: 2026-06-01. Raw markdown: https://promtable.com/glossary/agent-tracing.md.