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

Resource attributes get attached inconsistently depending on which SDK initialized first

In a process with more than one instrumentation source, whichever one sets up the resource information first wins, and the others silently inherit or override pieces of it depending on initialization order. Debugging why one service's traces are missing an expected tag usually comes down to import order in code nobody thought mattered. It is not something code review reliably catches.
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.