Wrong exporter selected for jaeger in OTEL_TRACES_EXPORTER

[treyhyde]

I believe, based on https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md#exporter-selection, that selecting jaeger for OTEL_TRACES_EXPORTER should use the agent exporter, not the collector exporter as set in https://github.com/open-telemetry/opentelemetry-ruby/blob/b7149fb72cad6c45956a6be80acfb2d062aab3a6/sdk/lib/opentelemetry/sdk/configurator.rb#L153

[fbogsany]

Technically, it is supposed to be the gRPC exporter, which we don't support. The closest equivalent is the CollectorExporter, not the AgentExporter.

[treyhyde]

I would love a way to select the AgentExporter which is the extreme preference with the OTEL environment variables. The jaeger value delivers to the agent in my other language stacks. Having consistency here in the otel community would be of great value.

[fbogsany]

The jaeger value delivers to the agent in my other language stacks.

It sounds like those aren't compliant with the spec, then. Unless they're using gRPC to the agent?

If someone adds a Jaeger exporter with gRPC support, we'll update the environment variable handling to use that. In the meantime, maybe we could add a jaegeragent value to configure the agent exporter?

[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.