[QUERY]: Is OpenTelemetry Baggage supported

[MarcusKohnert]

Library name and version

Azure.Messaging.ServiceBus 7.17.5

Query/Question

@lmolkova wrote here that OpenTelemetry Baggage will be gradually adopted once it is approved.

I couldn't find any information if that adoption took place already.
Here it sounds like it should work.

I couldn't get Baggage propagation over process boundaries working in my local development setup.

This is my scenario:

Process A, populates Baggage items via Activity.Current?.SetBaggage("", "")
Process A, sends message to Azure Service Bus
Process B, receives message from Azure Service Bus

Expected result:

Process B, Activity.Current has Baggage items

Actual result:

Process B, Activity.Current has no baggage

Is Baggage propagation already supposed to work?
If yes, do I need to turn on specific things (Flags or similar)?
Is maybe the transport mechanism to ServiceBus relevant?

Thanks for any hints or pointers?

Environment

dotnet --info
.NET SDK:
Version: 8.0.204
Commit: c338c7548c
Workload version: 8.0.200-manifests.7d36c14f
Runtime:
OS Name: Windows
OS Version: 10.0.19045
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\8.0.204\

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[jsquire]

@lmolkova : Would you mind offering your insight?

[lmolkova]

Thanks @MarcusKohnert !

The short answer is no, unfortunately Baggage is not supported - Azure/azure-sdk#6959
The long answer - we don't have a good way to support it in OTel-compatible way - open-telemetry/opentelemetry-dotnet#5667:

TL;DR: OTel does not recommend using Activity.Baggage and does not support propagating it. It has a separate baggage implementation outside of .NET BCL.
The propagation used by .NET is DistributedContextPropagator - its default implementation uses a different header name (Correlation-Context) than OTel (https://w3c.github.io/baggage/).

If we did use DistributedContextPropagator in .NET libraries, our .NET messaging would become incompatible with our instrumentation in other languages in the default case.

So the only viable path forward I see is to fix the problem on the OTel side before we can support baggage properly.

[github-actions]

Hi @MarcusKohnert. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

[MarcusKohnert]

@lmolkova Thank you very much for the explanation.