diff --git a/etc/kayobe/kolla/config/prometheus/rabbitmq.rules b/etc/kayobe/kolla/config/prometheus/rabbitmq.rules
index 82022d72a..324f0f3a3 100644
--- a/etc/kayobe/kolla/config/prometheus/rabbitmq.rules
+++ b/etc/kayobe/kolla/config/prometheus/rabbitmq.rules
@@ -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
diff --git a/releasenotes/notes/rm-rabbitmqtoomuchready-alert-a552b40e159d555c.yaml b/releasenotes/notes/rm-rabbitmqtoomuchready-alert-a552b40e159d555c.yaml
new file mode 100644
index 000000000..0cc335c0d
--- /dev/null
+++ b/releasenotes/notes/rm-rabbitmqtoomuchready-alert-a552b40e159d555c.yaml
@@ -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.