Skip to content
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.

Tolerate reads of 128 bit X-B3-TraceId #52

Merged
merged 1 commit into from
Sep 15, 2016
Merged

Tolerate reads of 128 bit X-B3-TraceId #52

merged 1 commit into from
Sep 15, 2016

Conversation

codefromthecrypt
Copy link
Contributor

The first step of transitioning to 128bit X-B3-TraceId is tolerantly reading 32 character long ids by throwing away the high bits (any characters left of 16 characters). This allows the tracing system to more flexibly introduce 128bit trace id support in the future.

Ex. when X-B3-TraceId: 463ac35c9f6413ad48485a3953bb6124 is received, parse the lower 64 bits (right most 16 characters ex48485a3953bb6124) as the trace id.

See openzipkin/b3-propagation#6

The first step of transitioning to 128bit `X-B3-TraceId` is tolerantly reading 32 character long ids by throwing away the high bits (any characters left of 16 characters). This allows the tracing system to more flexibly introduce 128bit trace id support in the future.

Ex. when `X-B3-TraceId: 463ac35c9f6413ad48485a3953bb6124` is received, parse the lower 64 bits (right most 16 characters ex48485a3953bb6124) as the trace id.

See openzipkin/b3-propagation#6
@yurishkuro
Copy link
Member

LGTM

@yurishkuro yurishkuro merged commit 9b067f1 into jaegertracing:master Sep 15, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants