-
Notifications
You must be signed in to change notification settings - Fork 641
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
[Regression] urllib3 downstream instrumentation not getting suppressed (with requests, boto3 upstream) #930
[Regression] urllib3 downstream instrumentation not getting suppressed (with requests, boto3 upstream) #930
Comments
Actually, I just tried this with an app that has
Not sure if |
Another update. This bug only happens with AUTO-instrumented applications. I tested using our Sample OTel Python apps which has Auto and Manual instrumentation. Maybe auto-instrumentation is instrumenting libraries twice? When I use manual instrumentation (modified to use the span_processor = BatchSpanProcessor(ConsoleSpanExporter())
trace.set_tracer_provider(
TracerProvider(
active_span_processor=span_processor,
id_generator=AwsXRayIdGenerator(),
)
)
I get this output (only 2 spans):
When I run the auto-insturmented application:
I get 3 spans:
|
Description
I thought that in #563 I had stopped calls to downstream Python packages from getting instrumented after instrumenting the AWS SDK.
However, my colleague @yimipeng discovered that DynamoDB calls still have
HTTP
traces fromurllib3
when he instrumentsbotocore
.For example, when using OTel Python instrumentation he sees this service map:
It's not until he adds this line:
that he sees the downstream
urllib3
traces disappear:His sample app which is already on GitHub is simple too:
In #563 I showed my changes fix this for S3. I wonder if it's possible it's different for DynamoDB? Or if anything else changed?
The text was updated successfully, but these errors were encountered: