🐛 Bug Report: Anthropic: after uninstrument(), a client that used with_raw_response / with_streaming_response stays traced through them
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- Mezza giornata
- Idoneità per principianti
- 62/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- python
- Ambito
- observability
Direzione di ricerca
Start with the reproduction script in the issue: it instruments, uses the plain, with_raw_response and with_streaming_response accessors on one client, then uninstruments and counts spans. The cause is that the SDK's cached accessor keeps a bound reference to the instrumented create, which AnthropicInstrumentor().uninstrument() does not reset. Done when all three lines print 0 spans, including for AsyncAnthropic.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Which component is this bug for?
Anthropic Instrumentation
📜 Description
After AnthropicInstrumentor().uninstrument(), calls made through client.messages.with_raw_response or client.messages.with_streaming_response are still traced, if that client used the accessor while the instrumentation was active. Plain client.messages.create(...) on the same client is correctly no longer traced, and a new client is fine.
The Anthropic SDK caches these accessor objects on the client (cached_property), and the cached wrapper keeps a reference to the instrumented create it was built from. uninstrument() restores the class method, but not the bound method inside the cached accessor, so those calls keep going through the instrumentation. The same happens with AsyncAnthropic.
(Unlike #4552 for OpenAI, where uninstrument() does nothing at all, the Anthropic instrumentation does uninstrument plain calls; only the cached accessors stay instrumented.)
👟 Reproduction steps
pip install anthropic opentelemetry-instrumentation-anthropic opentelemetry-sdk
import anthropic
from importlib.metadata import version
from anthropic._base_client import httpx2 as httpx # anthropic 1.x uses httpx2
from opentelemetry.sdk.trace import SpanProcessor, TracerProvider
from opentelemetry.instrumentation.anthropic import AnthropicInstrumentor
class Count(SpanProcessor):
n = 0
def on_end(self, span): Count.n += 1
provider = TracerProvider(); provider.add_span_processor(Count())
def respond(request): # local stand-in for the Anthropic API
return httpx.Response(200, json={"id": "msg_1", "type": "message", "role": "assistant", "model": "claude-x",
"content": [{"type": "text", "text": "Hello"}], "stop_reason": "end_turn",
"usage": {"input_tokens": 3, "output_tokens": 1}})
KW = dict(model="claude-x", max_tokens=10, messages=[{"role": "user", "content": "hi"}])
print(f"opentelemetry-instrumentation-anthropic {version('opentelemetry-instrumentation-anthropic')} | anthropic {version('anthropic')}")
for accessor in ("plain", "with_raw_response", "with_streaming_response"):
AnthropicInstrumentor().instrument(tracer_provider=provider)
client = anthropic.Anthropic(api_key="x", http_client=httpx.Client(transport=httpx.MockTransport(respond)))
def call():
if accessor == "plain":
client.messages.create(**KW)
elif accessor == "with_raw_response":
client.messages.with_raw_response.create(**KW)
else:
with client.messages.with_streaming_response.create(**KW) as r:
r.parse()
call() # used while instrumented
AnthropicInstrumentor().uninstrument()
Count.n = 0
call() # the same client, after uninstrument()
print(f"{accessor:24s} spans after uninstrument(): {Count.n}")
👍 Expected behavior
After uninstrument(), no call is traced, whichever accessor it goes through: 0 spans in all three lines.
👎 Actual Behavior with Screenshots
opentelemetry-instrumentation-anthropic 0.62.4 | anthropic 1.13.0
plain spans after uninstrument(): 0
with_raw_response spans after uninstrument(): 1
with_streaming_response spans after uninstrument(): 1
🤖 Python Version
3.12
📃 Provide any additional context for the Bug.
opentelemetry-instrumentation-anthropic 0.62.4 (the latest release); anthropic 1.13.0 and 1.11.0. The same happens for AsyncAnthropic. Related: #4552 (OpenAI, uninstrument() a no-op).
👀 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?
None
- Lingua principale
- Python
- Stelle
- 7.5k
- Fork
- 1.2k
- Merge medio
- 1g 23h
- PR unite (30g)
- 3
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 ·