-
Notifications
You must be signed in to change notification settings - Fork 897
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
Clarification on OTEL_SDK_DISABLED
scope
#4332
Comments
cc @open-telemetry/python-approvers @open-telemetry/java-approvers |
If you are using the Java autoconfigure module and set |
Thanks for clarifying, @trask. Is there a way for to use the Java SDK without the autoconfigure module? If so, does |
ya, you can use the Java SDK without the autoconfigure module, in which case |
Thanks, @trask! @open-telemetry/python-approvers - Am I reading your code correctly, will |
What are you trying to achieve?
Ruby received a PR to implement the
OTEL_SDK_DISABLED
environment variable, but we're not sure how far the functionality needs to go. The PR as it stands would skip creating providers through configuration, but someone could still manually create functional providers and tracers/meters/loggers. Is that acceptable?Additional context.
Here's the description:
I took a look at open-telemetry/opentelemetry-python#3648, and it seems like they always return no-ops when
OTEL_SDK_DISABLED
is true.However, Java's implementation seems closer to the Ruby PR. Configuration is skipped, but I don't know enough about Java to know if that means you cannot create working tracers, etc.
The text was updated successfully, but these errors were encountered: