feat(rules): when naming rules files use clear namespace separation #6482
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.
Description
Ref: #3468
I ran into the same issue that @janotav did with this comment. I want to be able to identify metrics from the Thanos Ruler around rule execution and failures and narrow them down to the
Namespace
andPrometheusRule
that they come from. The problem is the current naming pattern of$namespace-$rulename-$uid
doesn't account for resources that have-
's in the names... ie, the following rule creates a file namedmy-namespace-some-rule-thing-xxx-xxx-xxx-xxx-xxx
:The string
my-namespace-some-rule-thing-xxx-xxx-xxx-xxx-xxx
cannot be parsed through metric relabelings because you cannot definitively pull out thenamespace
andname
fields from the filename.Type of change
CHANGE
(fix or feature that would cause existing functionality to not work as expected)FEATURE
(non-breaking change which adds functionality)BUGFIX
(non-breaking change which fixes an issue)ENHANCEMENT
(non-breaking change which improves existing functionality)NONE
(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Verification
Due to #6284 - I was unable to fully test this locally.
Changelog entry
Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.