Skip to content
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

Add support for propagating "baggage" #13

Merged
merged 2 commits into from
Sep 18, 2023

Conversation

Gabriella439
Copy link
Contributor

@Gabriella439 Gabriella439 commented Sep 15, 2023

See: https://www.w3.org/TR/baggage/

While studying the traceparent/tracestatus-related logic, I noticed that there was a parallel W3C standard for a baggage header that one can propagate through a trace.

We're extremely unlikely to ever use this, but I figured it couldn't hurt to add this.

See: https://www.w3.org/TR/baggage/

While studying the `traceparent`/`tracestatus`-related logic, I noticed
that there was a parallel W3C standard for a baggage header that one
can propagate through a trace.

We're extremely unlikely to ever use this, but I figured it couldn't
hurt to add this.
Copy link
Owner

@parsonsmatt parsonsmatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice, thanks!

Mind adding a changelog entry? I can release as a patch version if you want to update version info too.

@parsonsmatt parsonsmatt merged commit 61595d9 into parsonsmatt:master Sep 18, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants