Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ceph: fix 'CephMonQuorumLost' alert #9068

Merged
merged 1 commit into from Nov 2, 2021
Merged

ceph: fix 'CephMonQuorumLost' alert #9068

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion cluster/examples/kubernetes/ceph/monitoring/prometheus-ceph-v14-rules.yaml
View file
Open in desktop
Expand Up @@ -90,7 +90,7 @@ spec:
severity_level: critical
storage_type: ceph
expr: |
count(kube_pod_status_phase{pod=~"rook-ceph-mon-.*", phase=~"Running|running"}) by (namespace) < 2
count(kube_pod_status_phase{pod=~"rook-ceph-mon-.*", phase=~"Running|running"} == 1) by (namespace) < 2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't the < 2 already cover the == 1 case?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

In the above example, we can see that if pod is in running phase value is 1 (at the right end). But if the pod is not running, the value is ZERO. So we have to collect / count pods which are in valid running state, that means the value is ONE.

for: 5m
labels:
severity: critical
Expand Down