-
Notifications
You must be signed in to change notification settings - Fork 386
feat(propagation): baggage support and automatic propagation #4505
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
Following up from #4371 which was merged with issues |
fdb6d56
to
8362c1e
Compare
Datadog ReportBranch report: ✅ 0 Failed, 20723 Passed, 1371 Skipped, 3m 19.55s Total Time |
4f76aad
to
8efab4f
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4505 +/- ##
==========================================
- Coverage 97.70% 97.69% -0.01%
==========================================
Files 1381 1383 +2
Lines 84017 84260 +243
Branches 4253 4278 +25
==========================================
+ Hits 82085 82321 +236
- Misses 1932 1939 +7 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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?
Tests were added in the repo and it passes the weblog system-tests. It will not pass the parametric system-tests because of the difficulty of managing the context in server.rb, not due an issue of implementation of the actual feature.