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

Update Zipkin toDomain to handle 128bit traceId and ipv6 #342

Conversation

pavolloffay
Copy link
Member

No description provided.

@pavolloffay pavolloffay force-pushed the zipkin-map-high-traceId-and-ipv6 branch from 4d8392d to 8a24026 Compare August 16, 2017 11:11
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 8a24026 on pavolloffay:zipkin-map-high-traceId-and-ipv6 into 5e5a361 on uber:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 8a24026 on pavolloffay:zipkin-map-high-traceId-and-ipv6 into 5e5a361 on uber:master.

@@ -61,7 +61,7 @@
}
},
{
"traceID": "1",
"traceID": "20000000000000001",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

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

Copy link
Contributor

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ot TraceIDFromString

@black-adder black-adder changed the title Zipkin update toDomain to handle 128bit traceId and ipv6 Update Zipkin toDomain to handle 128bit traceId and ipv6 Aug 16, 2017
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling a815bb5 on pavolloffay:zipkin-map-high-traceId-and-ipv6 into 5456a73 on uber:master.

@yurishkuro
Copy link
Member

done in #349

@yurishkuro yurishkuro closed this Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants