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

The collector pipeline configuration format is expressive enough to hide real mistakes

A processor ordered before the one it depends on produces no error, just data that is subtly wrong in a way nobody notices until a report looks off weeks later. Validating the pipeline requires understanding every processor's assumptions about what ran before it. Nothing in the tooling checks that ordering for you.
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.