Identifying otel http calls#5918
Conversation
Codecov ReportAttention:
... and 33 files with indirect coverage changes 📢 Thoughts on this report? Let us know! |
breedx-splk
left a comment
There was a problem hiding this comment.
Yeah this is a cool addition that will benefit Android. Thanks!
…nal/InstrumentationUtil.java Co-authored-by: jack-berg <[email protected]>
…nal/InstrumentationUtil.java Co-authored-by: jack-berg <[email protected]>
…r/sender/okhttp/internal/OkHttpHttpSenderTest.java Co-authored-by: jack-berg <[email protected]>
…r/sender/okhttp/internal/OkHttpGrpcSenderTest.java Co-authored-by: jack-berg <[email protected]>
|
Just want to get confirmation from @open-telemetry/java-instrumentation-maintainers that this strategy in core will allow instrumentation to accomplish the required suppression? A 👍 on this comment would be great. |
|
@LikeTheSalad can you open an issue to track adding suppression to the other exporters? Zipkin, grpc sender, and jaeger come to mind. |
…mmaryJavadoc" style warning
Sure, I've created 2 issues, one for Zipkin and the other for Jaeger:
I'm not sure if I might be missing something but I believe the changes in this PR should cover the grpc sender? |
Based on comments in the previous Java SIG meeting, I've created this approach to suppress automatic instrumentation using a Context key as it's done for Python.