- 2 minutes to read
RabbitMQ - Broker
The Nodinite RabbitMQ Monitoring Agent monitors all RabbitMQ nodes in the configured cluster.
- The Broker usage for RabbitMQ Brokers presents in Nodinite as a resource where the name of the resource is
ClusterName@NodeName
- 1 Resource per node in the cluster
- The
Broker
Resource Application name is associated with the name from the Display name property set by the Configuration - The Broker Resource is grouped by the Category Broker
Here's an example of a Monitor View filtered by the 'Broker' category.
What are the key features for Monitoring RabbitMQ broker?
- Cluster support - Verifies that all nodes in the cluster are operational (online)
- State Evaluation - Monitors and evaluates the run-time state
What is evaluated for the RabbitMQ Broker?
The evaluation rules for the RabbitMQ Broker are provided in the table below:
State | Status | Description | Actions | |
---|---|---|---|---|
Unavailable | Resource not available | Evaluation of the 'RabbitMQ Broker' is not possible either due to network or security-related problems | Review prerequisites | |
Error | Broker node error | Not implemented | ||
Warning | Broker node warning | If one of the nodes in a cluster setup is missing, or could not be reached | ||
OK | Online | All cluster nodes are available and the RabbitMQ broker is operational |
Tip
The evaluated state may be reconfigured using the Expected State functionality on every Resource within Nodinite.
Next Step
Add or manage Monitor View
Disk Thresholds
Memory Thresholds
Queue Thresholds