Skip to content

Jaeger Exporter does not handle SpanKind #369

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.

Sign up for GitHub

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

Jump to bottom
Closed
GoPavel opened this issue Jan 19, 2020 · 0 comments · Fixed by #387
Closed

Jaeger Exporter does not handle SpanKind #369

GoPavel opened this issue Jan 19, 2020 · 0 comments · Fixed by #387
Assignees
@mauriciovasquezbernal
Labels
exporters

Comments

@GoPavel
Copy link
Contributor

GoPavel commented Jan 19, 2020

Looks like Jaeger Exporter does not handle SpanKind field of spans during translation from OpenTelemetry's Span to Jaeger's Span.

In my opinion, we should just add 'span.kind' to attributes of Jaeger's Span.
Closed
@mauriciovasquezbernal mauriciovasquezbernal self-assigned this Jan 28, 2020
Merged
@c24t c24t closed this as completed in #387 Jan 30, 2020
srikanthccv pushed a commit to srikanthccv/opentelemetry-python that referenced this issue Nov 1, 2020
@danielkhan
Extend main README in preparation for Alpha (open-telemetry#369)
0c34096 
* fix(http-plugin): move node-sdk to dev deps

* docs: main readme

* docs: small fixes in wording

* fix: leftover space
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mauriciovasquezbernal mauriciovasquezbernal

Labels
exporters
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ext/jaeger: add span kind jaeger exporter kinvolk/opentelemetry-python
2 participants
@mauriciovasquezbernal @GoPavel