-
Notifications
You must be signed in to change notification settings - Fork 191
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
Do not validate instrumentation, if the whole SDK is disabled. #1453
Conversation
Do not validate instrumentation, if the whole SDK is disabled.
Thanks for opening your first pull request! If you haven't yet signed our Contributor License Agreement (CLA), then please do so that we can accept your contribution. A link should appear shortly in this PR if you have not already signed one. |
The committers listed above are authorized under a signed CLA. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1453 +/- ##
============================================
+ Coverage 73.26% 73.36% +0.09%
- Complexity 2685 2686 +1
============================================
Files 387 387
Lines 8009 8011 +2
============================================
+ Hits 5868 5877 +9
+ Misses 2141 2134 -7
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 4 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
This needs some thought. Per spec, disabling the SDK should still allow propagators: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md#general-sdk-configuration |
That's an interesting detail, I was missing.
Thank you for your help! |
I think it probably doesn't matter for rabbitmq (it's not performing distributed tracing). Our current thinking is that if the SDK is disabled, then when you fetch tracers/meters/loggers from the various providers, you'll get a no-op instance. |
@profuel thanks for your contribution, however we won't progress with this change due to the propagator thing - it would break some of our instrumentations according to spec. |
Do not validate instrumentation, if the whole SDK is disabled.