Ensure we respect OTEL instrumentation/signal configuration #131
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.
This ensures we respect the
OTEL_DOTNET_AUTO_INSTRUMENTATION_ENABLED
,OTEL_DOTNET_AUTO_{SIGNAL}_INSTRUMENTATION_ENABLED
andOTEL_DOTNET_AUTO_{SIGNAL}_{INSTRUMENTATION}_INSTRUMENTATION_ENABLED
family of environment variables.It follows the cascading rules as defined here: https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/docs/config.md#instrumentations
Renamed
ELASTIC_OTEL_ENABLE_ELASTIC_DEFAULTS
=>ELASTIC_OTEL_DEFAULTS_ENABLED
to fall more in line with other OTEL environment variable namesOn top of that we now support opting in to signals & instrumentations through
IConfiguration
.This now also lays the groundwork to enable/disable individual instrumentations.
I also took this opportunity to refactor the way we set
ConfigSource
a bit.