-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignore stdlib logs from urllib3 #135
Comments
+1 👍 |
Shouldn't the urllib3 instrumentation respect the contextvars to not infinite loop instrumentation? Are we maybe not propagating them correctly? |
This is urllib3 using stdlib logging, i.e. this fix would be in the stdlib logging instrumentation. The urllib3 instrumentation is not involved. But you do bring up a good point. Looking more closely, we use the string |
OTEL currently has a haphazard mix of suppress instrumentation keys. We should probably just set all of them. |
Well in this case it's about reading the correct key. OTEL conveniently sets it in the right places in BatchSpanProcessor and SimpleSpanProcessor. |
Fixed by #197 |
https://pydanticlogfire.slack.com/archives/C06EDRBSAH3/p1713885605381719
We can specifically ignore the message
https://logfire-api.pydantic.dev:443 "POST /v1/traces HTTP/1.1" 200 2
(and same for/v1/metrics
) so that the user doesn't have to silence all of urllib3 to avoid this noise.The text was updated successfully, but these errors were encountered: