-
Notifications
You must be signed in to change notification settings - Fork 2.4k
api: check silence matching by string comparison in getSilences #2443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
beorn7
merged 4 commits into
prometheus:master
from
ajalab:fix-get-silence-filter-regex
Feb 11, 2021
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f8c33ab
api: check silence matching by string comparison in getSilences
ajalab 72ce7fd
api: add test for gettableSilenceMatchesFilterLabels
ajalab b9aae07
Check silence matching with Protobuf models
ajalab b5ddc5d
Add test cases for silences with negative matchers
ajalab File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the new logic you have here were refactored into
matchFilterLabels, would it also improve alert filtering (sincematchFilterLabelsseems to be used by that endpoint too)?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I think it wouldn't. IMO we should apply different logic to filter alerts or silences.
For instance, suppose we'd like to filter alerts coming from
*.example.com-- we can use regexpinstance=~".*.example.com"for this purpose. In this case, we should rather apply the existingmatchFilterLabelslogic, which checks whether an alert label matches with the given matcher by using regexp.On the other hand, unlike alerts, a label of silence may contain regex like
instance=~".*.example.com"(silence all alerts from *.example.com). In this case, we should not use regexp to check whether the silence label matches with the given matcher, but apply a simple string comparison.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tend to agree with @ajalab .