Fix setting custom TracerProvider bug with no global TracerProvider
#37469
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
API change check API changes are not detected in this pull request. |
jeremydvoss
approved these changes
Sep 20, 2024
|
When will this be released? |
|
I have released a new version, PTAL: https://pypi.org/project/azure-monitor-opentelemetry-exporter/1.0.0b30/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#36363 introduced a bug that errors out if no global
TracerProvideris set before creating theAzureMonitorTraceExporter. Fixing this so that theexportcalls the global itself if no customTracerProviderwas used.Addresses: #37460