eG Monitoring
 

Measures reported by RabMQNodeStTest

Typically, at least one cluster node should be up and running at a given point in time, to keep the cluster alive. Client applications will be unable to access a RabbitMQ cluster if all its nodes are down. To ensure high cluster availability therefore, administrators should keep an eye on the running state of every node in the cluster and promptly identify the nodes that are not running, so that they can rapidly initiate measures to start the nodes that are down. This is where the RabMQNodeStTest test helps!

This test monitors the status of nodes in a cluster, and reports the count of nodes that are running and those that are down. Also, the test promptly notifies administrators if even a single node is rendered unavailable. Detailed diagnostics provided by this test reveal the name of the unavailable node(s), thus enabling administrators to start that node(s) and ensuring cluster availability.

Outputs of the test : One set of results for the cluster being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
totalNodes Indicates the total number of nodes in the cluster. Number  
runningNodes Indicates the number of nodes in the cluster that are currently running. Number Ideally, the value of this measure should be equal to that of the totalNodes measure.
stoppedNodes Indicates the number of nodes in the cluster that are not running presently. Number Ideally, the value of this measure should be 0. If this measure reports a non-zero value, then use the detailed diagnosis of the measure to know which nodes in the cluster are not running.