Skip to content

Remove RabbitMQ too much ready alert #1847

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

Merged
merged 1 commit into from
Aug 28, 2025
Merged

Remove RabbitMQ too much ready alert #1847

Show file tree
Hide file tree
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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 0 additions & 7 deletions etc/kayobe/kolla/config/prometheus/rabbitmq.rules
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,13 +41,6 @@ groups:
severity: warning
annotations:
description: RabbitMQ file descriptors usage on {{ $labels.instance }}
- alert: RabbitMQTooMuchReady
expr: rabbitmq_queue_messages_ready > 100
for: 1m
labels:
severity: warning
annotations:
description: RabbitMQ too much ready on {{ $labels.instance }}
- alert: RabbitMQTooMuchUnack
expr: rabbitmq_queue_messages_unacked > 100
for: 1m
Expand Down
10 changes: 10 additions & 0 deletions releasenotes/notes/rm-rabbitmqtoomuchready-alert-a552b40e159d555c.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
---
fixes:
- |
The ``RabbitMQTooMuchReady`` prometheus alert has been removed.

Since migrating to durable queues, messages are sent to all receivers, but
only one will respond. This results in high numbers of messages staying in
the ready state. The messages will be deleted automatically once they hit
resource limits. This appears to have no noticeable impact on CPU,
memory, or disk usage, so the alert is not needed.