-
Notifications
You must be signed in to change notification settings - Fork 888
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
Rename CorrelationContext to Baggage (again) #536
Comments
This should be closed by #517 no? |
I think this is a longer-term question than #517. It is both about the header name and the API concept name. W3C WG members raised concerns with the naming "correlation" as confusing & conflicting with other usages of the word. On the other hand, W3C "baggage" is very much a mechanism for user-supplied data, while OTEP 66 did an about face at the last moment from general purpose k/v bag to a more vague "observability-related correlation labels":
So this ticket, to me, is about whether OTel is going to support true baggage (which also completely covers observability concerns), or continue drawing a distinction between real baggage an OTel Correlations (in which case it should not be using the w3c "baggage" header). |
I think we should avoid figurative terms like "Baggage". The term itself is loaded with baggage at this point. How about calling this "User Data"? |
While the W3C baggage draft needs to become a formal recommendation, the W3C committee believes that it is now ready for implementation. No additional changes are expected, though it is possible (yet unlikely) that changes will occur as the spec goes through the formal W3C review process. Myself, @mwear , @dyladan , and @SergeyKanzhelev are on the W3C group. |
I think the W3C name should be stuck with to avoid confusion. If it is an implementation of W3C Baggage specification then it should be called "baggage". |
The W3C WG is leaning towards changing the
Correlation-Context
header name tobaggage
(w3c/baggage#17).What does this mean for OTel?
The text was updated successfully, but these errors were encountered: