-
Notifications
You must be signed in to change notification settings - Fork 361
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
MON-2727: Adds telemeter alert TelemeterClientFailures #1803
MON-2727: Adds telemeter alert TelemeterClientFailures #1803
Conversation
Issue: https://issues.redhat.com/browse/MON-2727 Problem: in-cluster admins and folks monitoring submitted Insights should have a way to figure out that the cluster is trying and failing to submit Telemetry. Solution: alert that will trigger when the rate of failed requests reaches a total of 20% of the total rate of requests in a 15 min window
abe25af
to
f7a2ab1
Compare
/skip |
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
/label px-approved For QE approval |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoaoBraveCoding, simonpasquier 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 |
checked with PR, used unauthorized token, since we pushed all metrics in one request, the maximum value for the TelemeterClientFailures expression is 1
and
|
/label qe-approved |
@JoaoBraveCoding: The following test 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. |
/retest |
Issue: https://issues.redhat.com/browse/MON-2727
Problem: in-cluster admins and folks monitoring submitted Insights should have a way to figure out that the cluster is trying and failing to submit Telemetry.
Solution: alert that will trigger when the rate of failed requests reaches a total of 20% of the total rate of requests in a 15 min window