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

Process additional Jaeger Span logs #3338

Closed
simitt opened this issue Feb 17, 2020 · 3 comments · Fixed by #6122
Closed

Process additional Jaeger Span logs #3338

simitt opened this issue Feb 17, 2020 · 3 comments · Fixed by #6122
Assignees
Labels

Comments

@simitt
Copy link
Contributor

simitt commented Feb 17, 2020

At the moment only error logs are processed and transformed into Elastic APM error events. Record additional Span Logs according to the OpenTracing spec.

Pick up previous discussion about investigating if it makes sense to introduce a dedicated Elastic APM convention for extended support.

@graphaelli
Copy link
Member

Linking to #3723. I had thought these would turn into transaction marks originally but generalizing them to actual logs would make them even more useful.

@axw axw added this to the 7.11 milestone Oct 13, 2020
@axw axw removed this from the 7.11 milestone Nov 4, 2020
@Dmitry31
Copy link

Dmitry31 commented Aug 11, 2021

Any future for this feature? There is no clear statement in the documentation about OpenTracing and OpenTelemetry logs support. Looking around on github I feel like Jaeger support is no more a priority as OpenTracing merged into OpenTelemetry ... But OpenTelemetry logs specs are in experimental state so no support neither?

@axw
Copy link
Member

axw commented Aug 11, 2021

@Dmitry31 Jaeger span logs are equivalent to OpenTelemetry span events, so when we get to #4715 we will be able to address this too.

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

Successfully merging a pull request may close this issue.

4 participants