🐛 Bug Report: Anthropic: since anthropic 1.14.0 each call reports its usage on two spans

Open
#4,700 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@simin-yuan is already working on this.

Since Nov 12, 2026.

  • #4703 by @simin-yuan — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start by reading the Anthropic instrumentation entry point where instrument() configures SDK behavior, then check the tests for environment variable handling and client creation order. Confirm the existing SDK switch prevents duplicate usage spans while preserving a caller's explicit setting, and verify the documented cases around clients created before instrumentation and streaming failures.

Written by the indexing model from the issue text.

Description

Which component is this bug for?

Anthropic Instrumentation

📜 Description

Since anthropic 1.14.0 the SDK starts its own span for each call by default when a global tracer provider is registered. With this instrumentation on top, each call reports its token usage on two spans, anthropic.messages.create and anthropic.chat, in two separate traces. A call with 1,000 input and 200 output tokens then costs $0.012 in the project totals of Phoenix 21.0.0 and Opik 2.2.143, where it should be $0.006 (raw responses, r2-A-lllatest, o1-A-lllatest).

👟 Reproduction steps
# double_span.py
import json
import threading
from http.server import BaseHTTPRequestHandler, HTTPServer

import anthropic
from opentelemetry import trace
from opentelemetry.instrumentation.anthropic import AnthropicInstrumentor
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import SimpleSpanProcessor
from opentelemetry.sdk.trace.export.in_memory_span_exporter import InMemorySpanExporter


class FakeAnthropic(BaseHTTPRequestHandler):
    def do_POST(self):
        self.rfile.read(int(self.headers["content-length"]))
        body = json.dumps({
            "id": "msg_1", "type": "message", "role": "assistant", "model": "claude-sonnet-5-5",
            "content": [{"type": "text", "text": "hi"}],
            "stop_reason": "end_turn", "stop_sequence": None,
            "usage": {"input_tokens": 1000, "output_tokens": 200},
        }).encode()
        self.send_response(200)
        self.send_header("content-type", "application/json")
        self.send_header("content-length", str(len(body)))
        self.end_headers()
        self.wfile.write(body)

    def log_message(self, *args):
        pass


server = HTTPServer(("127.0.0.1", 0), FakeAnthropic)
threading.Thread(target=server.serve_forever, daemon=True).start()

exporter = InMemorySpanExporter()
provider = TracerProvider()
provider.add_span_processor(SimpleSpanProcessor(exporter))
trace.set_tracer_provider(provider)
AnthropicInstrumentor().instrument()

client = anthropic.Anthropic(api_key="x", base_url=f"http://127.0.0.1:{server.server_port}")
client.messages.create(
    model="claude-sonnet-5-5", max_tokens=10, messages=[{"role": "user", "content": "hi"}]
)

for span in exporter.get_finished_spans():
    tokens = {k: v for k, v in span.attributes.items() if k in ("gen_ai.usage.input_tokens", "gen_ai.usage.output_tokens")}
    print(span.name, "|", span.instrumentation_scope.name, "|", tokens)
# anthropic 2.6.0, opentelemetry-instrumentation-anthropic 0.63.0, opentelemetry-sdk 1.45.2, Python 3.12
$ python double_span.py
anthropic.messages.create | com.anthropic.sdk.python | {'gen_ai.usage.input_tokens': 1000, 'gen_ai.usage.output_tokens': 200}
anthropic.chat | opentelemetry.instrumentation.anthropic | {'gen_ai.usage.input_tokens': 1000, 'gen_ai.usage.output_tokens': 200}
$ ANTHROPIC_OPEN_TELEMETRY=false python double_span.py
anthropic.chat | opentelemetry.instrumentation.anthropic | {'gen_ai.usage.input_tokens': 1000, 'gen_ai.usage.output_tokens': 200}
👍 Expected behavior

One span per call reports usage. The fix I'd pick: instrument() calls os.environ.setdefault("ANTHROPIC_OPEN_TELEMETRY", "false"). It uses the SDK's public switch, and a caller's own setting wins. Added after instrument() in the script above, it gives the anthropic.chat span alone. It does not reach a client created before instrument().

👎 Actual Behavior with Screenshots

Two spans with usage, as above.

🤖 Python Version

3.12

📃 Provide any additional context for the Bug.
  • Until #4536 and #4643 land, the SDK's span is the only record of a stream the app leaves early or of a sync stream that fails, so those should land first.
  • Arize-ai/openinference#4121 reaches every client by wrapping a private SDK function. Here it needs anthropic.chat current first, as #4366 does.
👀 Have you spent some time to check if this bug has been raised before?
  • I checked and didn't find similar issue
Are you willing to submit PR?

Yes I am willing to submit a PR!

Dominant language
Python
Stars
7.5k
Forks
1.2k
Avg merge
2d 6h
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from traceloop/openllmetry

All issues in traceloop/openllmetry

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.