-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add Baggage as Default Propagator #29060
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
Conversation
…_index.md Co-authored-by: Brian Marks <bm1549@users.noreply.github.com>
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.
Looks good.
We also describe the context propagation related config on the individual language configuration pages for example, Go so it would be good to make sure the correct defaults are documented on those pages as well.
Aside from this page, there are a handful of other pages that should be updated as well |
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
* Update DD_TRACE_PROPAGATION_STYLE default values * Update content/en/tracing/trace_collection/trace_context_propagation/_index.md Co-authored-by: Brian Marks <bm1549@users.noreply.github.com> * language section * Add baggage default propagator * updating all files --------- Co-authored-by: Brian Marks <bm1549@users.noreply.github.com>
* Update DD_TRACE_PROPAGATION_STYLE default values * Update content/en/tracing/trace_collection/trace_context_propagation/_index.md Co-authored-by: Brian Marks <bm1549@users.noreply.github.com> * language section * Add baggage default propagator * updating all files --------- Co-authored-by: Brian Marks <bm1549@users.noreply.github.com>
What does this PR do? What is the motivation?
baggage
propagator to docs and updates language portionsMerge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes