-
Notifications
You must be signed in to change notification settings - Fork 531
Add Alert Rule Classification Mapping enhancement #1917
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
base: master
Are you sure you want to change the base?
Add Alert Rule Classification Mapping enhancement #1917
Conversation
|
@simonpasquier @avlitman @machadovilaca Hi, |
1bd174b to
8daffb4
Compare
|
/unassign @moadz |
|
@sradco: The specified target(s) for Use DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/test markdownlint |
8daffb4 to
948ae4b
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
948ae4b to
86158ff
Compare
Signed-off-by: Shirly Radco <sradco@redhat.com>
86158ff to
f3756f0
Compare
|
@sradco: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This enhancement describes the alert rules classification
mapping details, logic and motivation.
This enhancements is related to #1822