Skip to content

Materialize scoped baggage on current span - #148

Closed
vrslev wants to merge 1 commit into
mainfrom
bugfix/VA-7612-current-span-baggage
Closed

Materialize scoped baggage on current span#148
vrslev wants to merge 1 commit into
mainfrom
bugfix/VA-7612-current-span-baggage

Conversation

@vrslev

@vrslev vrslev commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • extend opentelemetry_baggage_scope with an optional, explicit baggage-to-span attribute mapping
  • materialize supplied non-null values on an already-started recording span
  • preserve existing baggage propagation, exception snapshotting, and caller compatibility

This complements BaggageSpanProcessor: the processor covers server and consumer spans created after baggage exists, while the scope covers spans that start before an authoritative value becomes available.

Verification

  • just test tests/instruments/test_opentelemetry.py
  • just lint-ci
  • just test — 219 passed, 99% coverage
  • git diff --check
  • independent review: no material findings
@vrslev vrslev self-assigned this Aug 27, 2026
@codecov

codecov Bot commented Aug 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
unittests 99.01% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...obootstrap/instruments/opentelemetry_instrument.py 98.67% <100.00%> (+0.03%) ⬆️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
@vrslev vrslev changed the title VA-7612: Materialize scoped baggage on current span Aug 27, 2026
@vrslev vrslev closed this Aug 27, 2026
@vrslev
vrslev deleted the bugfix/VA-7612-current-span-baggage branch August 27, 2026 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant