-
Notifications
You must be signed in to change notification settings - Fork 2.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
Update Zipkin toDomain to handle 128bit traceId and ipv6 #342
Update Zipkin toDomain to handle 128bit traceId and ipv6 #342
Conversation
4d8392d
to
8a24026
Compare
@@ -61,7 +61,7 @@ | |||
} | |||
}, | |||
{ | |||
"traceID": "1", | |||
"traceID": "20000000000000001", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
traceID: {"hi": 1, "lo": 2}
did not worked
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checkout https://github.com/uber/jaeger/blob/5e5a361babba385bd0b9868bace1e10c75fc0829/model/span.go#L173 it overwrites the unmarshalling logic so that it can take a 128bit hex string and convert it into high and low
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ot TraceIDFromString
done in #349 |
No description provided.