Repository navigation
feat(trace): support the W3C random trace ID flag - #3718
ayush-that wants to merge 27 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3718 +/- ##
=======================================
+ Coverage 84.2% 84.6% +0.3%
=======================================
Files 123 123
Lines 30484 30894 +410
=======================================
+ Hits 25686 26144 +458
+ Misses 4798 4750 -48 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Pull request dashboard statusWaiting on maintainers · refreshed 2026-10-17 01:45 UTC Merge when ready. Status above doesn't look right?
|
lalitb
left a comment
There was a problem hiding this comment.
LGTM. Although the SDK randomness extension is still marked Development in the spec, Python and Java already expose it in their stable SDKs, so I’m comfortable following the same approach here, unless other @open-telemetry/rust-maintainers / @open-telemetry/rust-approvers have any concerns.
34b6b02 to
25ee034
Compare
25ee034 to
26d9998
Compare
|
hey @ayush-that , thanks for addressing comments! Can you resolve the conflict with main so we can merge this? |
Fixes #3270
Changes
Random trace IDs can now wear their little badge.
Adds RANDOM helpers, generator opt-in, SDK flag handling, and W3C propagation. Custom generators must implement
is_random()explicitly;RandomIdGeneratorreturnstrue. Children retain the flag even when dropped.B3's private deferred bit moves out of the way. Local drops clear it, and OTLP conversions filter private bits while preserving W3C flags.
Tests, Clippy, formatting, docs, and all precommit stages passed.
Merge requirement checklist