Verify Deep Agents Trace Export
Verify the local collector and downstream backend independently. Deep Agents work continues when export fails, so the agent exit status is not delivery evidence.
Set the Sandbox Name
Set the target sandbox in the host shell:
Verify Traces End to End
Run a short headless task to generate a managed trace:
Confirm that the collector received a trace batch and did not report a downstream exporter error:
The basic debug exporter prints a trace count without printing the full payload.
Open the project named by $LANGSMITH_PROJECT in the LangSmith UI.
Confirm that the new trace is present.
Both checks are required because the debug exporter can succeed while the remote exporter fails.
The LangSmith trace should include bounded model inputs and outputs. A representative tool task should also show bounded arguments and results on the tool span. LangGraph node scopes remain operation-only as described in Understand Deep Agents Trace Export.
Troubleshoot Trace Export
Use these checks to isolate each hop. For additional collector diagnostics, refer to Troubleshooting the OpenTelemetry Collector.
Related Topics
- Set Up Deep Agents Trace Export configures the policy and collector.
- Manage Deep Agents Trace Export covers stop, disable, reconfiguration, and removal operations.
- Understand Deep Agents Trace Export explains privacy and trust boundaries.
- Troubleshooting covers broader sandbox and runtime failures.