-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
test/extended/prometheus: add test validating alert severity #26016
Conversation
24e2569
to
3fa5a1a
Compare
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.
/lgtm
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: paulfantom, simonpasquier The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3fa5a1a
to
ee8b429
Compare
New changes are detected. LGTM label has been removed. |
7674ef9
to
f9b993e
Compare
f9b993e
to
7735be5
Compare
7735be5
to
6202d4f
Compare
/test e2e-metal-ipi-ovn-ipv6 |
2 similar comments
/test e2e-metal-ipi-ovn-ipv6 |
/test e2e-metal-ipi-ovn-ipv6 |
881fb47
to
c28b8da
Compare
/approve |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: paulfantom, simonpasquier The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
c28b8da
to
da8d9d9
Compare
As per the "Alerting Consistency" enhancement, alerts should have a `severity` label and this label should be one of "critical", "warning" or "info". This change adds a test verifying that all alerting rules shipped as part of OpenShift comply with this requirement. [1] https://github.com/openshift/enhancements/blob/master/enhancements/monitoring/alerting-consistency.md Signed-off-by: Simon Pasquier <spasquie@redhat.com>
da8d9d9
to
77a50e2
Compare
/retest |
/test e2e-aws-serial |
2 similar comments
/test e2e-aws-serial |
/test e2e-aws-serial |
@smarterclayton can you have another look please? The test should report all alerting rules that don't have a severity label or define a severity value other than |
@simonpasquier: The following tests failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
@smarterclayton friendly ping |
/assign @derekwaynecarr |
/close Closing this (if I can) in favor of #26476. |
@bison: Closed this PR. In 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/test-infra repository. |
In the context of openshift/enhancements#637, this change adds a test that ensures all alerting rules shipped by core components follow the established standards. In particular, all alerting rules must have a
severity
label and the value should be eitherinfo
,warning
orcritical
(theWatchdog
alert is the only exception).