-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
jaeger exporter missing critical data #1160
Comments
There is no If the investigation leads to the code in this repo we can look into it. |
@tigrannajaryan good question! We're using the jaeger exporter. The error message (span_processer.go) is coming from Jaeger's code. When I talked to the Jaeger people about it, they said that the problem is that opentelemetry-collector is not sending the right data, see discussion here: jaegertracing/jaeger#2300 |
(To be clear, I do not have enough expertise to know if this is a jaeger bug or an opentelemetry bug, I'm just trying to make sure that both sides have enough information to figure out the problem!) |
@pavolloffay please help us identify if this is on our side or jaeger side :) |
I will have a look at a first glance it looks like data translation issue. |
I wasn't able to reproduce this with https://github.com/open-telemetry/opentelemetry-go/blob/master/example/basic/main.go#L68 and
The wasn't any error log in Jaeger. However the service name was set to an empty string which does not work properly with Jaeger UI. |
I got the error, it happens when the
This has been fixed in #1222. This issue can be closed. |
Closing this per comment in #1160 (comment) |
yay thanks! |
The jaeger_span was never destroyed after its release from the JaegerRecordable. This change let a `std::unique_ptr` handle the destruction when going out of scope, first allowing the `thrift::Span` to be copied to the `span_buffer_`.
Describe the bug
I'm playing around with setting up opentelemetry with Jaeger for the first time, and Jaeger is spewing errors. They look like this:
Steps to reproduce
I'm using:
I have a pretty good isolated repro that I can create a repo for, if that would be helpful. It basically just uses the off-the-shelf docker containers for opentelemetry-collector and jaeger, plus the sample code for opentelemetry-go
What did you expect to see?
No error
What did you see instead?
The error above
What version did you use?
What config did you use?
Environment
docker
Additional context
I also filed this bug upstream against Jaeger
jaegertracing/jaeger#2300
They believe that opentelemetry is missing critical data here
The text was updated successfully, but these errors were encountered: