-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat: extract/inject datadog tracestate field p
#115
Conversation
9e3ee6c
to
28e2b0c
Compare
Add support for W3C datadog tracestate field `p`.
28e2b0c
to
674b5bf
Compare
p
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -300,6 +308,7 @@ Expected<ExtractedData> extract_w3c( | |||
return result; | |||
} | |||
|
|||
result.datadog_w3c_parent_id = "0000000000000000"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious to know: Is there a reason to use 0s id instead of an empty field somehow? Is the all 0s value a special value somewhere else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's from the RFC. I think it's an optimization for the backend.
Description
Add support for W3C datadog tracestate field
p
.