-
Notifications
You must be signed in to change notification settings - Fork 545
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
Alerts for failing OLM operators #1104
Alerts for failing OLM operators #1104
Conversation
b84eed6
to
64525b5
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
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.
Great work on this @anik120! One issue that needs to be addressed, but looks good otherwise!
/retest |
/test e2e-aws-olm |
64525b5
to
f358251
Compare
3ca37d4
to
bf784ab
Compare
bf784ab
to
1a68799
Compare
/retest |
1 similar comment
/retest |
- Add prometheus rule for firing an alert when csv_abnormal metric is emitted with phase=failed - Alert message contains name and version of operator.
1a68799
to
0d3a9c2
Compare
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anik120, awgreene, ecordell The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test e2e-aws-console-olm |
1 similar comment
/test e2e-aws-console-olm |
Description of the change:
is emitted with phase=failed
Motivation for the change:
As a OpenShift administrator, I want to be able to receive a notification when an operator is consistently reaching a failed state so that I can immediately address known issues.
Enhancement proposal
Reviewer Checklist
/docs