-
Notifications
You must be signed in to change notification settings - Fork 381
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(propagation): baggage support and automatic propagation #4371
base: master
Are you sure you want to change the base?
Conversation
👋 Hey @DataDog/ruby-guild, please fill "Change log entry" section in the pull request description. If changes need to be present in CHANGELOG.md you can state it this way **Change log entry**
Yes. A brief summary to be placed into the CHANGELOG.md (possible answers Yes/Yep/Yeah) Or you can opt out like that **Change log entry**
None. (possible answers No/Nope/None) Visited at: 2025-02-20 19:01:38 UTC |
e9d741c
to
eee20a9
Compare
Datadog ReportBranch report: ✅ 0 Failed, 20684 Passed, 1371 Skipped, 3m 7.51s Total Time |
eee20a9
to
751ca10
Compare
7919272
to
64cb8a6
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4371 +/- ##
==========================================
+ Coverage 97.74% 97.75% +0.01%
==========================================
Files 1351 1353 +2
Lines 82697 82908 +211
Branches 4198 4222 +24
==========================================
+ Hits 80831 81047 +216
+ Misses 1866 1861 -5 ☔ View full report in Codecov by Sentry. |
…b into zachg/baggage_support
What does this PR do?
Following the spec here: https://www.w3.org/TR/baggage/ we implement baggage for the Ruby tracer. The otel drop in support will be added in a future PR.
Motivation:
Change log entry
Additional Notes:
How to test the change?