proposal: relabel action to drop target/sample when any label value matches#90
Open
RajeshRajendiran wants to merge 1 commit into
Open
Conversation
…atches Signed-off-by: Rajesh Rajendiran <rajeshrajendirandev@gmail.com>
RajeshRajendiran
force-pushed
the
relabel-drop-if-any-label-matches
branch
from
July 8, 2026 21:09
ed6fbc7 to
4b3dd8d
Compare
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.
This proposal addresses prometheus/prometheus#14057 — a relabel action
(tentatively
dropifany) that drops a target or sample when the regexmatches the value of any of its labels, so operators can block
well-known high-cardinality value patterns (IDs, emails, generated
hostnames) without knowing in advance which label will carry them.
Filed per the bug-scrub guidance from @krajorama and @alexgreenbank on
the issue, which asked for a design doc here as the starting point. The
doc covers the foot-gun concern, naming, and the alternatives discussed
in the issue and in #13664 / #12483.