Skip to content

Document alert firing after RMQ queue migrations#2194

Open
MoteHue wants to merge 1 commit intostackhpc/2025.1from
rmq-upgrade-document-firing-alert
Open

Document alert firing after RMQ queue migrations#2194
MoteHue wants to merge 1 commit intostackhpc/2025.1from
rmq-upgrade-document-firing-alert

Conversation

@MoteHue
Copy link
Contributor

@MoteHue MoteHue commented Mar 3, 2026

No description provided.

@MoteHue MoteHue requested a review from a team as a code owner March 3, 2026 13:26
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a note to the OpenStack upgrade documentation, informing operators about the RabbitMQTooMuchReady Prometheus alert that may fire after migrating RabbitMQ queues. This is a helpful addition to prevent confusion during an upgrade. My review includes a suggestion to improve the phrasing and formatting of the new note for better clarity and consistency with the rest of the document.


After 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, so the Prometheus alert RabbitMQTooMuchReady will start
Copy link
Member

Choose a reason for hiding this comment

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

nit: I'd wrap RabbitMQTooMuchReady in double backticks, but I'm not going to hold up the PR for it

Suggested change
the ready state, so the Prometheus alert RabbitMQTooMuchReady will start
the ready state, so the Prometheus alert ``RabbitMQTooMuchReady`` will start

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants