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

Define OpenTelemetry to Jaeger span Transformation #414

Closed
mauriciovasquezbernal opened this issue Jan 20, 2020 · 2 comments
Closed

Define OpenTelemetry to Jaeger span Transformation #414

mauriciovasquezbernal opened this issue Jan 20, 2020 · 2 comments
Labels
area:semantic-conventions Related to semantic conventions priority:p2 Medium priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:trace Related to the specification/trace directory

Comments

@mauriciovasquezbernal
Copy link
Member

Jaeger is one of the recommended exporters that the SDKs should support [1], however there is not a specification about how the transformation from the OpenTelemetry to the Jaeger Spans should work.

It is already causing some confusion as the implementation in different languages is different, open-telemetry/opentelemetry-python#367 (comment) & open-telemetry/opentelemetry-python#369.

There is an open PR handling this for Zipkin #380, probably there should also be a similar document for Jaeger.

[1] https://github.com/tigrannajaryan/opentelemetry-specification/blob/master/specification/library-guidelines.md#requirements.

@bogdandrutu bogdandrutu added the spec:trace Related to the specification/trace directory label Jun 12, 2020
@bogdandrutu bogdandrutu added the area:semantic-conventions Related to semantic conventions label Jun 26, 2020
@carlosalberto carlosalberto added the release:required-for-ga Must be resolved before GA release, or nice to have before GA label Jul 2, 2020
@andrewhsu andrewhsu added the priority:p2 Medium priority level label Jul 17, 2020
@andrewhsu andrewhsu added release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs and removed release:required-for-ga Must be resolved before GA release, or nice to have before GA labels Sep 25, 2020
@andrewhsu
Copy link
Member

from the issue triage mtg today with TC, allowing changes related to this issue for GA if editorial changes only

@carlosalberto
Copy link
Contributor

I'm going to close this one as we indeed added this but we removed it after some time (see #3964), i.e.

Jaeger exporter support will be removed from OpenTelemetry in July 2023.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:semantic-conventions Related to semantic conventions priority:p2 Medium priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:trace Related to the specification/trace directory
Projects
None yet
Development

No branches or pull requests

4 participants