Allow external exporters in `OTEL_TRACES_EXPORTER`

[jtmalinowski]

Currently OpenTelemetry::SDK::Configurator#wrapped_exporters_from_env uses a hard-coded case-when list of exporters. I'm proposing that we make the list extendable.

A use case for the same easy configuration process (ENV-based) for vendors with their own exporters. For example setting OTEL_TRACES_EXPORTER=console,otlp-<vendor name> would enable both the console exporter and an instance of OTLP exporter configured to send data to the vendor.

This idea could be extended to metrics, but I'm not familiar with the current status of metrics.

This idea could be extended to propagators, but I don't currently see a good use case for this, as the list is quite complete. Core team can advise here.

I can submit the PR for this issue, if we agree an a solution.

[plantfansam]

@jtmalinowski to make sure I understand, you're saying that the configurator's add_span_processor method is not a satisfactory solution because a env var-based configuration is more user-friendly?

[github-actions[bot]]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.