Fix KubernetesStatefulsetDown prom rule
This commit is contained in:
@@ -319,8 +319,11 @@ spec:
|
|||||||
summary: Kubernetes PersistentVolume error (instance {{ $labels.instance }})
|
summary: Kubernetes PersistentVolume error (instance {{ $labels.instance }})
|
||||||
description: "Persistent volume is in bad state\n VALUE = {{ $value }}\n LABELS = {{ $labels }}"
|
description: "Persistent volume is in bad state\n VALUE = {{ $value }}\n LABELS = {{ $labels }}"
|
||||||
- alert: KubernetesStatefulsetDown
|
- alert: KubernetesStatefulsetDown
|
||||||
expr: (kube_statefulset_status_replicas_ready / kube_statefulset_status_replicas_current) != 1
|
# compare against spec replicas: status_replicas_current is 0 on
|
||||||
for: 1m
|
# healthy statefulsets after rollouts (false positives), and a
|
||||||
|
# ready/desired division breaks on scale-to-zero (0/0 = NaN)
|
||||||
|
expr: kube_statefulset_status_replicas_ready < kube_statefulset_replicas
|
||||||
|
for: 5m
|
||||||
labels:
|
labels:
|
||||||
severity: critical
|
severity: critical
|
||||||
annotations:
|
annotations:
|
||||||
|
|||||||
Reference in New Issue
Block a user