From 4d845425e652a109abe7f61c3460e947d3e797f8 Mon Sep 17 00:00:00 2001 From: Arun Kumar Mohan Date: Mon, 4 Oct 2021 10:29:53 +0530 Subject: [PATCH] ceph: reverting the time delay of 'CephMonHighNumberOfLeaderChanges' As 'CephMonHighNumberOfLeaderChanges' means there is a multiple monitor election and indicate some communication issue between the monitors. Increasing interval timing for this alert is not considered as safe. So reverting this change back to 5m Signed-off-by: Arun Kumar Mohan --- .../kubernetes/ceph/monitoring/prometheus-ceph-v14-rules.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cluster/examples/kubernetes/ceph/monitoring/prometheus-ceph-v14-rules.yaml b/cluster/examples/kubernetes/ceph/monitoring/prometheus-ceph-v14-rules.yaml index a21ed9a14b45..bfa23c71903d 100644 --- a/cluster/examples/kubernetes/ceph/monitoring/prometheus-ceph-v14-rules.yaml +++ b/cluster/examples/kubernetes/ceph/monitoring/prometheus-ceph-v14-rules.yaml @@ -91,7 +91,7 @@ spec: storage_type: ceph expr: | (ceph_mon_metadata{job="rook-ceph-mgr"} * on (ceph_daemon) group_left() (rate(ceph_mon_num_elections{job="rook-ceph-mgr"}[5m]) * 60)) > 0.95 - for: 15m + for: 5m labels: severity: warning - name: ceph-node-alert.rules