W3C distributed tracing-compatible operation id
See original GitHub issueCurrently, ApplicationInsights SDKs support Request-Id header for correlation that looks like |<root-id>.
W3C distributed tracing protocol is going to replace current Request-Id
format and is being implemented in ApplicationInsights SDKs.
The first phase of implementing it is a change of the rootId format.
Currently it’s 5 base64 chars, but to enable compatibility with W3C standard, it should be 32 chars [a-z][0-9], lowercase. All zeros is considered invalid.
Example of the valid id: 0af7651916cd43dd8448eb211c80319c
.
It could be implemented as a lowercase guid without dashes or 16 random bytes encoded into hex string.
The rest: header names and hierarchy in Request-Id could still be preserved (i.e. |0af7651916cd43dd8448eb211c80319c.
is a valid Request-Id).
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
Added in #973
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.