Agent Tracing

7 Best Agent Tracing Tools (LangSmith, Langfuse, Phoenix)

Compare agent tracing tools for inspectable runs: prompts, tool calls, retrieved context, errors, retries, cost, and latency.

Search intent

Choose tracing tooling for debugging production agents and explaining why a run made a decision.

Last reviewed

June 23, 2026

Tools considered

12

Open source options

9

Definition

Agent tracing records the execution path of a run so developers can debug decisions instead of guessing from the final response.

Use cases

  • Debugging failed tool calls
  • Reviewing retrieved evidence and intermediate messages
  • Monitoring latency and cost across model/tool steps

Selection criteria

  • Does the trace include tool arguments and outputs?
  • Can sensitive data be redacted before storage?
  • Can traces feed evaluation and support workflows?

Selection advice

Tracing should be installed before the first serious user pilot. Without traces, every agent bug becomes anecdotal.

Tool comparison snapshot

ToolBest forOpen sourceMain tradeoffOpen
LangSmithagent tracingNoteams that cannot send traces to a hosted serviceOpen
Langfuseself-hosted agent tracingYesteams that only need a hosted LangChain-native workflowOpen
Arize Phoenixagent tracingYesteams that already have a paid observability contractOpen
Heliconelow-friction production tracingYesteams that need deep span-level agent debugging onlyOpen
Braintrustexperiment-driven agent iterationNoteams that only need lightweight trace viewingOpen
TraceloopOpenTelemetry-first agent tracingYesteams without an observability backendOpen
LangWatchconversation-level agent monitoringYesteams that only need raw OpenTelemetry exportOpen