Skip to main content
Anthropic provides the Claude family of large language models. Arize AX captures every Anthropic SDK call — prompts, responses, tool calls, and token usage — via the OpenInference instrumentors for Python, JavaScript / TypeScript, and Go, so you can debug, evaluate, and monitor Claude-powered applications.

Prerequisites

Launch Arize AX

  1. Sign in to your Arize AX account.
  2. From Space Settings, copy your Space ID and API Key. You will set them as ARIZE_SPACE_ID and ARIZE_API_KEY below.

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

  1. Open your Arize AX space and select project anthropic-tracing-example.
  2. You should see a new trace within ~30 seconds containing an LLM span — messages.create for the Python SDK, Anthropic Messages for the Node.js SDK, or anthropic.messages.create for the Go SDK — with the prompt, response, and token usage attached.
  3. 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.
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 each messages.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

The trace tree in Arize AX is 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_ID and ARIZE_API_KEY are set in the same shell that runs the example. Enable OpenTelemetry debug logs with export OTEL_LOG_LEVEL=debug and re-run.
  • Anthropic spans missing but other spans present (Python). AnthropicInstrumentor().instrument(...) must run before any import anthropic in the application. Make sure instrumentation.py is the first import in your entry point.
  • 401 from Anthropic. Verify ANTHROPIC_API_KEY is set and has access to the model in the example. Swap claude-sonnet-4-6 for a model your key can call.
  • Go process exits before spans flush. arize-otel-go uses a batched span processor by default. The defer tp.Shutdown(...) block in main.go is what flushes the batch — without it, short-lived programs lose their last spans. Pass SimpleProcessor: true to arizeotel.Register if you want synchronous export instead.

Resources

Anthropic Documentation

OpenInference Anthropic Instrumentor (Python)

OpenInference Anthropic Instrumentor (JavaScript / TypeScript)

Anthropic Tracing Example (messages.create)

Anthropic Tracing Example (tool calling)

Anthropic Go SDK

OpenInference Anthropic Instrumentor (Go)