-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 set TraceProvider to global #5138
Conversation
Codecov Report
@@ Coverage Diff @@
## main #5138 +/- ##
==========================================
+ Coverage 89.90% 89.94% +0.03%
==========================================
Files 182 182
Lines 11080 11077 -3
==========================================
+ Hits 9962 9963 +1
+ Misses 892 889 -3
+ Partials 226 225 -1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should already be a non-issue since the provider in the TelemetrySettings
should be used by all components. Definitely good to eliminate this, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably worth a changelog in case this breaks anyone using the global provider.
The reason is because soon we will have the config for the tracing/metrics providers in the main config (already started). When this happens then we can have users "reconfigure" that via the watch API, and re-setting the global is not allowed in otel (also not restart friendly). Because of that we should break this behavior now, and not install the global. Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
@codeboten thanks for reminding me... I forgot to push the changes :)) |
…cs featuregate enabled This PR also removes the set of the global MeterProvider, similarly with open-telemetry#5138. Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
…cs featuregate enabled This PR also removes the set of the global MeterProvider, similarly with open-telemetry#5138. Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
…cs featuregate enabled This PR also removes the set of the global MeterProvider, similarly with open-telemetry#5138. Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
…cs featuregate enabled This PR also removes the set of the global MeterProvider, similarly with open-telemetry#5138. Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
…cs featuregate enabled This PR also removes the set of the global MeterProvider, similarly with open-telemetry#5138. Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
The reason is because soon we will have the config for the tracing/metrics providers in the main config (already started). When this happens then we can have users "reconfigure" that via the watch API, and re-setting the global is not allowed in otel (also not restart friendly). Because of that we should break this behavior now, and not install the global. Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
…cs featuregate enabled (open-telemetry#5146) This PR also removes the set of the global MeterProvider, similarly with open-telemetry#5138. Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
The reason is because soon we will have the config for the tracing/metrics providers in the main config (already started).
When this happens then we can have users "reconfigure" that via the watch API, and re-setting the global is not allowed in otel (also not restart friendly). Because of that we should break this behavior now, and not install the global.
Signed-off-by: Bogdan Drutu bogdandrutu@gmail.com