Investigate ways to Customise the KuberhealthyDeploymentCheck Alert (is it of use to us)?
Closed this issue · 2 comments
pwyborn commented
Service name
Kuberhealthy:
KuberhealthyDeploymentCheck Alert
Problem description
For some time I have felt that this is alert is on only being set off when there are problems with Kuberhealthy itself. It results in swamping #lower-priority-alarms with alerts.
Can we customise so that it is actually alerting us to problems on the cluster itself.
The runbook should actually point to a course of action that should always be taken.
See also (for alerting messages in past):
https://docs.google.com/spreadsheets/d/1vO7dZMK9pORXVFLHywUihoCnDlmI7T-UTIWPq4j5k-8/edit#gid=307107938
https://docs.google.com/spreadsheets/d/1vO7dZMK9pORXVFLHywUihoCnDlmI7T-UTIWPq4j5k-8/edit#gid=0
pwyborn commented
Matt-Alinosn commented
Closing as new discovery ticket around Kuberhealthy.