Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move B3 and Jaeger trace propagators #2228

Closed
breedx-splk opened this issue Dec 8, 2020 · 2 comments
Closed

Move B3 and Jaeger trace propagators #2228

breedx-splk opened this issue Dec 8, 2020 · 2 comments
Labels
Feature Request Suggest an idea for this project

Comments

@breedx-splk
Copy link
Contributor

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.

@breedx-splk breedx-splk added the Feature Request Suggest an idea for this project label Dec 8, 2020
@jkwatson
Copy link
Contributor

jkwatson commented Dec 8, 2020

I'd like some resolution on open-telemetry/oteps#142 before making this decision.

@bogdandrutu
Copy link
Member

I think it is too late for this :) Long live jaeger and zipkin in the extensions/trace-propagators

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Suggest an idea for this project
Projects
None yet
Development

No branches or pull requests

3 participants