Prototype passing a Customizer Class to the Configurator #4469
Conversation
This file contains hidden or 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
This was referenced Mar 10, 2025
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.
Add a generic Customizer class with methods for initializing the exporters and the resource, it could be extended to customize all the initialization done by the configurator.
The lets vendors customize auto instrumentation in a way that isn't possible right now with just environment variables.
GoogleCloudPlatform/opentelemetry-operations-python#388 -- this is an example of what an implementation of the Customizer class by a vendor might look like.
See open-telemetry/opentelemetry-python-contrib#3353 for the change that'd be needed for contrib