v3.0.0 RC1 imposes tracecontext as propagation about traefik

[rtribotte]

Hello @jcchavezs,

Thanks for opening this!

Indeed, in v3 we reworked the tracing feature completely to support only OpenTelemetry and instrumenting only with OpenTelemetry SDK, with, as the first intention, trace context propagation, as OpenTelemetry follows the W3C Trace Context specification.

The reason is that although traefik supports tracecontext, applications have to do their tracing theirselves and forcing them all to migrate towards is not a trivial task (are the tracing libraries they use compatible with tracecontext? are they willing to upgrade or reimplement tracing for this?). I suggest you either allow it being configurable (otel already supports many propagation models opentelemetry-go-contrib/propagators at main · open-telemetry/opentelemetry-go-contrib · GitHub 2) or support both tracecontext and b3 as most of the tracers support b3.

This makes sense, and we are open to considering integrating other propagation models and are eager to read community feedback on this.
We are marking this issue as a proposal accordingly.

[jcchavezs]

Awesome!

[jcchavezs]

Ping @zetaab given that he worked out migration from OT to OTel.

[rtribotte]

Hello,

We do think that multiple propagation models should be possible to configure, and we are marking this issue as an enhancement.

For that, we are working on supporting the OTEL_PROPAGATORS environment variable: https://opentelemetry.io/docs/languages/sdk-configuration/general/#otel_propagators.

[rtribotte]

I think this issue is solved by #10465, I'm closing it accordingly.