Some of the content described in this article is available in meshIQ Manage versions 12.1 and greater.
For a quick overview of what's new or changed, visit the meshIQ Highlights page for a version-by-version breakdown.
Jump to Section:
Version 12.x and Later
Version 11.3 and Earlier
Version 12.x and Later
The Check Health feature in RabbitMQ allows you to verify the operational status of different server components. These health checks help confirm whether essential services—such as alarms, listeners, certificates, and cluster-critical processes—are functioning correctly.
When you run a health check:
If the component is healthy, the Status field displays ok.
If the component is not healthy or does not meet the expected condition, the Status field remains empty.
Some checks require additional input such as protocol name, port number, or time window.
Run a Health Check
To perform a health check:
Open the Server widget and select the RabbitMQ server.
From the Selected menu, choose Check Health.
The RabbitMQ Server Check Health dialog opens. Choose a Health Check Of option from the dropdown.
Provide any required inputs (if applicable) and click Check Health.
View the result in the Status field (and Reason, when provided).
Health Check Options
Below are all available health check options and what each one validates:
1. Alarms
Checks if any system-wide alarms (e.g., memory or disk alarms) are active.
Healthy state: No alarms present.
2. Local Alarms
Checks alarms specific to the selected node.
Healthy state: No local alarms raised.
3. Certificate Expiration
Checks whether server certificates are nearing expiration.
Requires input:
Within – number of units
Unit – days/weeks/months/years.
Healthy state: All certificates valid beyond the specified time window.
4. Port Listener
Verifies whether a specific TCP port is actively listening.
Requires input:
Port number
Healthy state: The port is open and accepting connections.
5. Protocol Listener
Checks whether a listener for a given protocol (e.g., AMQP, MQTT) is running.
Requires input:
Protocol name
Healthy state: Listener is active for the specified protocol.
6. Virtual Host
Checks the health of all virtual hosts on the server, confirming they can respond to basic operations.
Healthy state: All virtual hosts respond correctly.
7. Node Mirror Sync. Critical
Checks whether all mirrored queues on the node have fully synchronized mirrors.
Healthy state: All mirrors are in sync. If not, the Status field remains empty.
8. Quorum Critical
Checks if quorum queues are in a critical sync state.
Healthy state: No critical quorum issues.
Example output may also show a Reason such as single node cluster.
____________________________________________________________________________________________________________
Version 11.3 and Earlier
The Check Health feature in RabbitMQ allows you to verify the operational status of different server components. These health checks help confirm whether essential services—such as alarms, listeners, certificates, and cluster-critical processes—are functioning correctly.
When you run a health check:
If the component is healthy, the Status field displays ok.
If the component is not healthy or does not meet the expected condition, the Status field remains empty.
Some checks require additional input such as protocol name, port number, or time window.
Run a Health Check
To perform a health check:
Open the Server viewlet and select the RabbitMQ server.
From the Selected menu, choose Check Health.
The RabbitMQ Server Check Health dialog opens. Choose a Health Check Of option from the dropdown.
Provide any required inputs (if applicable) and click Check Health.
View the result in the Status field (and Reason, when provided).
Health Check Options
Below are all available health check options and what each one validates:
1. Alarms
Checks if any system-wide alarms (e.g., memory or disk alarms) are active.
Healthy state: No alarms present.
2. Local Alarms
Checks alarms specific to the selected node.
Healthy state: No local alarms raised.
3. Certificate Expiration
Checks whether server certificates are nearing expiration.
Requires input:
Within – number of units
Unit – days/weeks/months/years.
Healthy state: All certificates valid beyond the specified time window.
4. Port Listener
Verifies whether a specific TCP port is actively listening.
Requires input:
Port number
Healthy state: The port is open and accepting connections.
5. Protocol Listener
Checks whether a listener for a given protocol (e.g., AMQP, MQTT) is running.
Requires input:
Protocol name
Healthy state: Listener is active for the specified protocol.
6. Virtual Host
Checks the health of all virtual hosts on the server, confirming they can respond to basic operations.
Healthy state: All vhosts respond correctly.
7. Node Mirror Sync. Critical
Checks whether all mirrored queues on the node have fully synchronized mirrors.
Healthy state: All mirrors are in sync. If not, the Status field remains empty.
8. Quorum Critical
Checks if quorum queues are in a critical sync state.
Healthy state: No critical quorum issues.
Example output may also show a Reason such as single node cluster.