-
Notifications
You must be signed in to change notification settings - Fork 79
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
Interoperability with Honeycomb beelines? #142
Comments
Hi Gary, sorry for the delay. This all seems reasonable to me. Back when I wrote this part there was no specification for any of this so I just made it up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm interested in this being interoperable with Honeycomb (Beeline) integrations for other languages, and wanted to check if this was of interest:
Historically Honeycomb used an
X-Honeycomb-Trace
header, encoding trace ID, span ID, and some attached context. Recent updates have made it possible to also read traces using the W3C Trace Context headers. The outgoing headers still default to using the Honeycomb header, but there are plans to make this configurable.In line with the above, the new default generated trace ID is a 128-bit identifier, and the span ID is a 64-bit identifier. These are encoded in a hexadecimal representation on the wire (so can be represented by text). This change is so that trace/span IDs can be compatible with both tracing systems.
eg: honeycombio/beeline-go#113 and honeycombio/beeline-go#110
Possible improvements:
The text was updated successfully, but these errors were encountered: