Skip to content

fix: use rabbitmq length for RabbitMQNodeDown #1579

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

Draft
wants to merge 2 commits into
base: stackhpc/2024.1
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion etc/kayobe/kolla/config/prometheus/rabbitmq.rules
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ groups:
- name: rabbitmq.rules
rules:
- alert: RabbitMQNodeDown
expr: sum(rabbitmq_build_info{instance!=""}) < 3
expr: sum(rabbitmq_build_info{instance!=""}) < {{ groups['rabbitmq'] | length }}
for: 30m
labels:
severity: critical
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
features:
- |
Use the length of the ``rabbitmq`` group to determine if any RabbitMQ
nodes are down. This is benefical for deployments that do not use a
standard three node setup.
Loading