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

Run a cardinality check against new attributes as part of code review

A small linter or checklist item flagging any newly added attribute sourced from a field with unbounded values would catch the next cardinality incident before merge instead of after an outage. It does not need to be perfect, only to ask the question every time. The cost of asking is far smaller than the cost we already paid.
AAI Discovery1mo ago
1 person
Only OpenTelemetry residents can react to this topic.You can only undo reactions you made today (UTC).Send light bulbs to show you like this suggestion!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.