-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Empty tag is being added after conversion from zipkin #2595
Comments
If this is internal span, why does it specify remote endpoint? |
the simpler fix is to add jaeger/cmd/collector/app/zipkin/jsonv2.go Lines 108 to 115 in 8388432
and handle nil in the caller jaeger/cmd/collector/app/zipkin/jsonv2.go Lines 83 to 87 in 8388432
|
We're using opentelemetry collector with zipkin exporter, it gets spans from opentelemetry-js SDK. I think there can also be an issue in one of them (collector or js sdk). But in any case it worth fixing it here too. Took me quite some time to understand what's going on. |
it's worth fixing here, a switch without default clause is not the most robust approach anyway. |
#2595 Signed-off-by: Marian Zagoruiko <[email protected]>
Describe the bug
When receiving zipkin spans, a tag with empty tag name is being added.
To Reproduce
Steps to reproduce the behavior:
tags-as-fields: all: true
.remoteEndpoint
property != null. The's an example attached.Expected behavior
Spans should be saved in ES, empty tags shouldn't be added.
I did some debugging, and seems like the issue is in
spanV2ToThrift
function, specifically here:https://github.com/jaegertracing/jaeger/blob/8388432/cmd/collector/app/zipkin/jsonv2.go#L82
There's no default case in this switch in
remoteEndpToThrift
function:https://github.com/jaegertracing/jaeger/blob/8388432/cmd/collector/app/zipkin/jsonv2.go#L108
So for "internal" spans it will be empty.
I'd suggest not to add tags with empty key name, maybe check it here: https://github.com/jaegertracing/jaeger/blob/8388432/cmd/collector/app/zipkin/jsonv2.go#L87
Version (please complete the following information):
Additional context
Jaeger config:
Sample zipkin span:
Jaeger logs when trying to process such span:
The text was updated successfully, but these errors were encountered: