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
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
| Tool | Best for | Open source | Main tradeoff | Open |
|---|---|---|---|---|
| LangSmith | agent tracing | No | teams that cannot send traces to a hosted service | Open |
| Langfuse | self-hosted agent tracing | Yes | teams that only need a hosted LangChain-native workflow | Open |
| Arize Phoenix | agent tracing | Yes | teams that already have a paid observability contract | Open |
| Helicone | low-friction production tracing | Yes | teams that need deep span-level agent debugging only | Open |
| Braintrust | experiment-driven agent iteration | No | teams that only need lightweight trace viewing | Open |
| Traceloop | OpenTelemetry-first agent tracing | Yes | teams without an observability backend | Open |
| LangWatch | conversation-level agent monitoring | Yes | teams that only need raw OpenTelemetry export | Open |