opentelemetry-dotnet-instrumentation
opentelemetry-dotnet-instrumentation copied to clipboard
Use `OTEL_{SIGNAL}_EXPORTER` to handle console exporter
Feature Request
Are you requesting automatic instrumentation for a framework or library? Please describe.
- 1.4.0 and current main
Is your feature request related to a problem? Please describe.
Spec changed 3 months ago: https://github.com/open-telemetry/opentelemetry-specification/commit/d72b0da79645432c62593f074c64ae44778680aa
Describe the solution you'd like
Support console for OTEL_TRACES_EXPORTER, OTEL_METRICS_EXPORTER, and OTEL_LOGS_EXPORTER.
Describe alternatives you've considered
N/A
Additional context
What to do with OTEL_DOTNET_AUTO_TRACES_CONSOLE_EXPORTER_ENABLED, OTEL_DOTNET_AUTO_METRICS_CONSOLE_EXPORTER_ENABLED, and OTEL_DOTNET_AUTO_LOGS_CONSOLE_EXPORTER_ENABLED.
What to do with OTEL_DOTNET_AUTO_TRACES_CONSOLE_EXPORTER_ENABLED, OTEL_DOTNET_AUTO_METRICS_CONSOLE_EXPORTER_ENABLED, and OTEL_DOTNET_AUTO_LOGS_CONSOLE_EXPORTER_ENABLED.
I recommend considering a phased approach before discontinuing support. First, introduce a minor release where the env vars are marked as deprecated in documentation. Simultaneously, issue warnings (e.g., to the console) when users interact with the deprecated environment variables, conveying their impending removal in the subsequent minor release. This provides users with a clear transition period.