Claude Platform observability with OpenTelemetry

​

Prerequisites

• A Bronto API key with the Ingestion role. See API Keys.
• Your Bronto region: eu or us.
• For API tracing: the admin role in your Claude Console organization.
• For SDK tracing: a Claude SDK version with OpenTelemetry support (Python, TypeScript, Go, Java, C#, PHP, or Ruby). The examples below use Python 3.10 or later.

​

Send API traces from the Claude Console

1. In the Claude Console, open Settings → OpenTelemetry (direct link) and click Add destination.
2. Fill in the form:

   Field	Value
   Provider	Custom
   Name	For example, Bronto EU
   OTLP endpoint URL	https://ingestion.eu.bronto.io or https://ingestion.us.bronto.io
   Request headers	Name x-bronto-api-key, value your Bronto API key
   Content mode	Metadata only or Full content. See Prompts and responses.
   Workspaces	All, or only the workspaces you want to trace

   Enter the base URL without /v1/traces. The Claude API appends /v1/traces itself, so a URL that already ends in /v1/traces fails with an HTTP 404.

3. Click Add destination. To send a test span, open the destination’s More actions menu and click Test. An anthropic.test span is delivered to Bronto.
4. Send a request from a covered workspace, for example from the Console playground or with curl. Within about a minute, the destination’s Delivery column changes from No data to Healthy.

​

Add the destination with the Admin API

curl --fail-with-body -sS "https://api.anthropic.com/v1/organizations/telemetry_destinations" \
  -H "x-api-key: $ANTHROPIC_ADMIN_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "anthropic-beta: telemetry-destinations-2026-08-11" \
  -H "content-type: application/json" \
  -d '{
    "endpoint_url": "https://ingestion.<REGION>.bronto.io",
    "headers": {"x-bronto-api-key": "<BRONTO_API_KEY>"},
    "traces": {"content_mode": "metadata_only"},
    "workspaces": {"type": "all"}
  }'

​

Send SDK traces from your application

pip install anthropic opentelemetry-sdk opentelemetry-exporter-otlp-proto-http

export OTEL_SERVICE_NAME="support-agent"
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://ingestion.<REGION>.bronto.io/v1/traces"   # eu or us
export OTEL_EXPORTER_OTLP_TRACES_HEADERS="x-bronto-api-key=<YOUR_API_KEY>"
export ANTHROPIC_API_KEY="<YOUR_CLAUDE_API_KEY>"

from opentelemetry import trace
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
from opentelemetry.sdk.resources import Resource
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor

# Register the tracer provider before the first Claude call.
provider = TracerProvider(resource=Resource.create())  # reads OTEL_SERVICE_NAME
provider.add_span_processor(BatchSpanProcessor(OTLPSpanExporter()))  # reads OTEL_EXPORTER_OTLP_TRACES_*
trace.set_tracer_provider(provider)
tracer = trace.get_tracer("support-agent")

from anthropic import Anthropic, beta_tool

client = Anthropic()


@beta_tool
def get_order_status(order_id: str) -> str:
    """Look up the status of an order.

    Args:
        order_id: The order ID, e.g. "A-1001".
    """
    return f"{order_id}: shipped yesterday"


with tracer.start_as_current_span("handle_ticket"):
    runner = client.beta.messages.tool_runner(
        model="claude-haiku-5-5",
        max_tokens=1024,
        tools=[get_order_status],
        messages=[{"role": "user", "content": "Where is my order A-1001?"}],
    )
    for message in runner:
        pass
    print(message.content[-1].text)

provider.shutdown()  # flush spans before a short-lived process exits

​

What you’ll see in Bronto

​

One trace from your code to the model

handle_ticket                                   support-agent      your span
└─ anthropic.messages.tool_runner               support-agent      SDK
   ├─ anthropic.messages.create      CLIENT     support-agent      SDK, request 1
   │  └─ anthropic.messages.create   SERVER     claude-platform    API
   │     └─ anthropic.model_request             claude-platform    API, one per model run
   ├─ anthropic.custom_tool_use get_order_status support-agent     SDK, your tool
   └─ anthropic.messages.create      CLIENT     support-agent      SDK, request 2 with the tool result
      └─ anthropic.messages.create   SERVER     claude-platform    API
         └─ anthropic.model_request             claude-platform    API

​

Span attributes

​

Search and aggregate

"$span.name" = 'anthropic.model_request' AND "$gen_ai.request.model" = 'claude-haiku-5-5'

"$service.name" = 'claude-platform' AND "$span.name" LIKE 'anthropic.tool_use%' AND "$span.status_code" = 'STATUS_CODE_ERROR'

​

Prompts and responses

• Metadata only (default): identifiers, timing, status, token counts, model names, and the names and descriptions of your agents and tools.
• Full content: also the system prompt (gen_ai.system_instructions), the messages sent (gen_ai.input.messages), the response (gen_ai.output.messages), and tool arguments and results. Content follows the GenAI “parts” format, for example [{"role":"user","parts":[{"type":"text","content":"…"}]}]. Each span holds up to 0.75 MB of content by default. Longer content is shortened and the span gets anthropic.content.truncated = true.

​

Troubleshooting

​

References

• On-call Copilot lab: a runnable example app that produces the traces on this page
• LLM Observability
• Send Traces to Bronto
• Explore Traces
• OpenTelemetry for the Claude API
• Use OpenTelemetry with the Claude API (destinations)
• Use OpenTelemetry with the Claude SDK
• OpenTelemetry span reference
• OpenTelemetry GenAI semantic conventions