I had recently done a write-up on OpenTelemetry baggage, the lesser-known OpenTelemetry signal that helps manage metadata across microservices in a distributed system.
This is helpful for sending feature flags, parameter IDs, etc. without having to add support for them in each service along the way. For example, if your first service adds a `use_beta_feature` flag, you don't have to add logic to parse and re-attach this flag to each API call in the service. Instead, it will be propagated across all downstream services via auto-instrumentation, and whichever service needs it can parse, modify and/or use the value.
I'd love to discuss and understand your experience with OTel baggage or other aspects you found that maybe weren't as well-discussed.
dhruv_ahuja•2h ago
I had recently done a write-up on OpenTelemetry baggage, the lesser-known OpenTelemetry signal that helps manage metadata across microservices in a distributed system.
This is helpful for sending feature flags, parameter IDs, etc. without having to add support for them in each service along the way. For example, if your first service adds a `use_beta_feature` flag, you don't have to add logic to parse and re-attach this flag to each API call in the service. Instead, it will be propagated across all downstream services via auto-instrumentation, and whichever service needs it can parse, modify and/or use the value.
I'd love to discuss and understand your experience with OTel baggage or other aspects you found that maybe weren't as well-discussed.