You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We think it makes short-term sense to continue treating the extensions/trace-propagators like a "contrib" space to contain 3rd-party/contributed propagators (see the conversation in #2207). With that, it makes less sense to leave the B3 and Jaeger propagators there, because they are first-party, supported propagators.
Let's move those two propagators into the opentelemetry-api-trace module (api/trace) and have them live in the io.opentelemetry.api.trace.propagation package as peers of the W3CTraceContextPropagator.
The text was updated successfully, but these errors were encountered:
We think it makes short-term sense to continue treating the
extensions/trace-propagators
like a "contrib" space to contain 3rd-party/contributed propagators (see the conversation in #2207). With that, it makes less sense to leave the B3 and Jaeger propagators there, because they are first-party, supported propagators.Let's move those two propagators into the
opentelemetry-api-trace
module (api/trace
) and have them live in theio.opentelemetry.api.trace.propagation
package as peers of theW3CTraceContextPropagator
.The text was updated successfully, but these errors were encountered: