Closed AdamCoulterOz closed 4 months ago
@AdamCoulterOz Thanks for your feedback! We will investigate and update as appropriate.
Thank you for reaching out to us! We appreciate your interest in improving our documentation.
The feedback channel on GitHub is designed for updating documentation with known information, and we will not be able to provide a timely response to your question here. Please also note that GitHub issues are being phased out completely. For more information see: https://aka.ms/ContentUserFeedback.
The best way to get answers to your questions is to create a support ticket. Our support team is available to assist you with any questions or issues you may have. You can create a support ticket by visiting the following link: https://azure.microsoft.com/support/create-ticket/
Once you have received assistance from our support team, we would be happy to document the answer to your questions in the appropriate articles for future reference. #please-close
I'm seeking clarification on the apparent discrepancies regarding the ID size and uniqueness requirements for distributed trace-related telemetry items, as well as their mapping to the W3C TraceContext standards. This is highlighted in the following document sections:
Data model for telemetry correlation
Noting the specifically called out globally unique requirement for all distributed trace related telemetry items (i.e.
Request
andDependency
, but technically should also includePageView
too). This is achieved using GUIDs with theseID
fields being 16 bytes.Example
The example table is nice and clear in how then mapping occurs, but uses very short
ID
fields (which may just be for ease of reading) which I doubt those4
and12
byte IDs are globally unique.Correlation headers using W3C TraceContext
Finally, the mapping of
Request
andDependency
Id
fields to theparent-id
field of the W3C TraceContext. Theparent-id
field is only8
bytes. How can I fit a16
byte guid into a8
byte parent-id ?Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.