-
Notifications
You must be signed in to change notification settings - Fork 135
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
Baggage items not propagated to span's descendants #363
Milestone
Comments
buranmert
added a commit
that referenced
this issue
Jan 12, 2021
BaggageItems.get(key) searches in parent.baggageItems too
buranmert
added a commit
that referenced
this issue
Jan 12, 2021
BaggageItems.get(key) searches in parent.baggageItems too
buranmert
added a commit
that referenced
this issue
Jan 12, 2021
BaggageItems.get(key) searches in parent.baggageItems too
buranmert
added a commit
that referenced
this issue
Jan 12, 2021
BaggageItems.get(key) searches in parent.baggageItems too
buranmert
added a commit
that referenced
this issue
Jan 12, 2021
BaggageItems.get(key) searches in parent.baggageItems too
hi again @philtre 👋 we made a fix and it will be in the next release 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
As I was testing out various Datadog features, I noticed that baggage items set in a span are not propagated to its descendants.
It seems that the
OTSpan.baggageItem(withKey:)
only returns the baggage item if it was set directly on the span, and does not query the span's parent.This is also evident from the implementation of
DDSpan
andBaggageItems
:The only way to access the parent span's baggage items is to iterate through all of then in
DDSpanContext
:The documentation for
OTSpan.baggageItem(forKey:)
does not specify whether this is expected behavior.Suggestions
If this is expected behavior, adding a note in the
OTSpan.baggageItem(forKey:)
would be very useful.If
OTSpan.baggageItem(forKey:)
is expected to return ancestor baggage items, thenBaggaggeItems
could be modified in the following way:The text was updated successfully, but these errors were encountered: