Prerequisites
- Python 3.10+, Node.js 18+, or Go 1.25+
- An Arize AX account (sign up)
- An
ANTHROPIC_API_KEYfrom the Anthropic Console
Launch Arize AX
- Sign in to your Arize AX account.
- From Space Settings, copy your Space ID and API Key. You will set them as
ARIZE_SPACE_IDandARIZE_API_KEYbelow.
Install
Configure credentials
Setup tracing
Go SDK Only
/v1/messages is instrumented today. Streaming responses pass through unchanged, but output.value and token counts are not populated for streaming spans yet. tool_use content blocks in messages are not yet captured as message.tool_calls attributes — wrap your tool execution in manual TOOL spans, see Manual instrumentation.Run Anthropic
Expected output
Verify in Arize AX
- Open your Arize AX space and select project
anthropic-tracing-example. - You should see a new trace within ~30 seconds containing an LLM span —
messages.createfor the Python SDK,Anthropic Messagesfor the Node.js SDK, oranthropic.messages.createfor the Go SDK — with the prompt, response, and token usage attached. - If no traces appear, see Troubleshooting.
Check from the skill, CLI, or SDK
Confirm spans are actually reaching your Arize AX project. Use whichever fits your workflow — the skill and CLI work for any framework; the SDK check is shown for each language.- Arize skill (agent)
- AX CLI
- SDK
Install the Arize Skills plugin and let your coding agent check for you:Then prompt your agent:
Use the arize-trace skill to export and analyze recent traces from my project. Confirm spans are arriving, and summarize any errors or latency issues.
Trace tool usage
The instrumentor traces eachmessages.create call automatically, including the tool calls Claude requests. It does not trace your application executing those tools, or the loop that feeds results back to the model. To capture the full agent trace, wrap the loop in a manual chain span and each tool execution in a manual tool span with the OpenTelemetry API — the auto LLM spans nest under your chain span automatically. See Combine auto and manual instrumentation for the pattern.
Expected output
weather-agent (chain span) → two LLM spans → one get_weather tool span.
Go SDK The auto middleware still emits an LLM span for each
Messages.New call, but it does not populate tool_use blocks as attributes on that span. The chain and tool spans are created manually with the OpenTelemetry API — threading the chain span’s ctx into each Messages.New call is what nests the auto LLM spans underneath it.Troubleshooting
- No traces in Arize AX. Confirm
ARIZE_SPACE_IDandARIZE_API_KEYare set in the same shell that runs the example. Enable OpenTelemetry debug logs withexport OTEL_LOG_LEVEL=debugand re-run. - Anthropic spans missing but other spans present (Python).
AnthropicInstrumentor().instrument(...)must run before anyimport anthropicin the application. Make sureinstrumentation.pyis the first import in your entry point. 401from Anthropic. VerifyANTHROPIC_API_KEYis set and has access to the model in the example. Swapclaude-sonnet-4-6for a model your key can call.- Go process exits before spans flush.
arize-otel-gouses a batched span processor by default. Thedefer tp.Shutdown(...)block inmain.gois what flushes the batch — without it, short-lived programs lose their last spans. PassSimpleProcessor: truetoarizeotel.Registerif you want synchronous export instead.