Mateusz Łach

Baggage propagation - known issues

1

This issue lists known issues related to baggage propagation. - https://github.com/open-telemetry/opentelemetry-dotnet/issues/5260 - https://github.com/open-telemetry/opentelemetry-dotnet/issues/5479 - https://github.com/open-telemetry/opentelemetry-dotnet/issues/5677

### Package OpenTelemetry.Api ### Package Version | Package Name | Version | | ------------------------------------- | ------- | | OpenTelemetry.Api | 1.8.0 (and previous versions) | ### Runtime Version any ###...

Clarify how compliant implementations should handle invalid baggage entries

2

There is inconsistency related to how invalid baggage entries are handled by some existing implementations (e.g [java implementation](https://github.com/open-telemetry/opentelemetry-java/blob/788347e262b34ccf287a5b32a9976eb43e170c5f/api/all/src/main/java/io/opentelemetry/api/baggage/propagation/W3CBaggagePropagator.java) ignores invalid entries on both `inject`/`extract`, and propagate valid ones; [go implementation](https://github.com/open-telemetry/opentelemetry-go/blob/047df28b88f837688fd7ab3ea9d92c3495d8c0c3/baggage/baggage.go#L394)...

[Definition](https://w3c.github.io/baggage/#definition) section defines `value` as a 0 or more repetitions of `baggage-octet`. > value = *baggage-octet Taking that into account, it is allowed for a `list-member` to have no `value`....

# Feature Request **Additional context** Implement improvements for RabbitMQ client bytecode instrumentation: - add network tags to `deliver` spans - add baggage support for `deliver` spans - target additional consumer...