-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add cluster-info recording rule #931
Conversation
- expr: |- | ||
avg by (cluster_id, customer, installation) ( | ||
label_replace( | ||
capi_cluster_info, |
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.
CAPI clusters
"name", | ||
"(.*)" | ||
) | ||
or cluster_operator_cluster_status |
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.
Vintage WCs
or cluster_operator_cluster_status | ||
or cluster_service_cluster_info | ||
or | ||
label_replace( |
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.
Management clusters
1470252
to
763f439
Compare
Signed-off-by: QuentinBisson <[email protected]>
763f439
to
6330dee
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.
looks nice !
Before adding a new alerting rule into this repository you should consider creating an SLO rules instead.
SLO helps you both increase the quality of your monitoring and reduce the alert noise.
Towards: https://github.com/giantswarm/giantswarm/issues/28268
This PR adds a recording rule to be able to list all clusters to be used in join with absent functions
Checklist
oncall-kaas-cloud
GitHub group).