OpenObserve

Does O2 expose Baggage at all in traces? Would that even be a good idea?

Baggage isn't directly exposed as a separate field in O2 today. It’s request-scoped context that gets propagated across services, and it only shows up in the trace if the application/collector explicitly converts it into span attributes.

I think exposing it could be useful, especially for debugging cross-service context, but we'd need to consider the security/privacy implications since Baggage can contain sensitive data.