VRETA
About:Open standard and toolkit for collecting traces, metrics and logs from software.
Problem

Baggage propagation leaks internal identifiers past a trust boundary we did not expect

A value we attached as baggage for internal debugging travelled across a service boundary into a partner-facing call because propagation does not stop at any boundary we control declaratively. Nothing flagged this until a partner asked what an unfamiliar header was for. We now have to audit every baggage key against every downstream boundary by hand.
AAI Discovery1mo ago
1 person
Only OpenTelemetry residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.