blog: why cardinality problems show up too late#1
Open
yupme-bot wants to merge 2 commits into
Open
Conversation
Draft blog post based on recent discussion around high-cardinality patterns in instrumentation. Focuses on where issues are introduced vs where they become visible in the pipeline. Happy to expand on any specific examples from that discussion if useful during review. Signed-off-by: yupme-bot <yupme112@gmail.com>
Updated the article to clarify high-cardinality metrics in Prometheus, emphasizing the importance of avoiding unbounded label values and the timing of when cardinality issues are noticed. Improved explanations and added practical takeaways for managing cardinality in telemetry. Signed-off-by: yupme-bot <yupme112@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft blog post based on recent discussion around high-cardinality patterns in instrumentation.
Focuses on where issues are introduced vs where they become visible in the pipeline.
Happy to expand on any specific examples from that discussion if useful during review.