🐛 Bug Report: Anthropic: since anthropic 1.14.0 each call reports its usage on two spans
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 56/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- python
- Ambito
- backend, observability
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.chatcurrent 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!
- Lingua principale
- Python
- Stelle
- 7.5k
- Fork
- 1.2k
- Merge medio
- 2g 6h
- PR unite (30g)
- 2
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di traceloop/openllmetry
-
🐛 Bug Report: OpenAI Responses: with_raw_response.create() raises when the body can't be parsed, though the uninstrumented call returnsForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug python
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
traceloop/openllmetry#4717 ·
I maintainer di solito rispondono entro 1 giorno
-
🐛 Bug Report: Incomplete cache token migration after #4243 breaks Bedrock and Groq instrumentationForse già presa @Quantum-Enigma-dot l’ha presa 21 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
traceloop/openllmetry#4665 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
🐛 Bug Report: OpenAI instrumentation drops gen_ai.usage.reasoning_tokens on streamed chat completionsForse già presa @jayfeng7 l’ha presa 23 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
traceloop/openllmetry#4660 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Bug Report: Failed dataset deletes still remove local rows and columnsForse già presa @inchang-ing l’ha presa 32 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
traceloop/openllmetry#4630 ·
I maintainer di solito rispondono entro 1 giorno
-
🐛 Bug Report: LiteLLM instrumentation does not record seed, stop, frequency_penalty, presence_penaltyForse già presa @shantam77 l’ha presa 38 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
traceloop/openllmetry#4598 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di traceloop/openllmetry
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
mozilla-ai/cq#601 ·
I maintainer di solito rispondono entro 1 giorno
-
Bump Python to 3.14 or 3.15Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
intcomma returns exponential notation for large floatsForse già presa @Omarinho12345 l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
python-humanize/humanize#521 ·
I maintainer di solito rispondono entro 1 giorno
-
LUCJ pass manager raises NoEdgeBetweenNodes when an edge is bad for two two-qubit gatesForse già presa @hat-im l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itForse già presa @paulo-0308 l’ha presa oggi. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
Diaoul/subliminal#1405 ·