Monitoring a Clustered RabbitMQ setup in APM
For Monitoring RabbitMQ, Applications Manager uses the Management Plugin provided by default RabbitMQ installations to collect performance metrics. The Management plugin provides a series of API endpoints required to monitor the target RabbitMQ instance. The following are the list of endpoints utilized by Applications Manager to collect performance metrics for a target RabbitMQ instance:
- /api/nodes
- /api/queues
- /api/exchanges
- /api/connections
- /api/channels
Monitoring a Clustered RabbitMQ setup
In Applications Manager, you can only monitor single node setups of RabbitMQ instances. Applications Manager does not support clustering for RabbitMQ monitor yet. While this is yet to be supported, you can still monitor a Clustered RabbitMQ setup efficiently without adding every single node in the clusters as individual monitors.
Before proceeding any further, we need to take the following points into account,
- All nodes are equal peers in a RabbitMQ Cluster.
- Management plugin can be enabled in any node present in a Clustered RabbitMQ setup.
- Management Plugin can be used to view/collect information pertaining to an entire cluster from any node that is present in the cluster setup.
Since the Management Plugin can be enabled in any node present in the Clustered RabbitMQ instance and because every node points to the same data that pertains to a entire cluster, it is not necessary to enable the Management Plugin in every node present in the cluster. You do not need to add them as individual monitors either as they will be considered as duplicate monitors.
Alternatively, Management plugin can be enabled in any one of the RabbtiMQ nodes present in a Clustered RabbitMQ setup which can then can be added as a single monitor in Applications Manager. This will be used to monitor all the components present in the entire cluster. This approach will reduce considerable load on both Applications Manager and the target RabbitMQ instances.
While the Clustered RabbitMQ components can be monitored using a single RabbitMQ monitor, you can monitor the RabbitMQ processes individually by adding them as separate server monitors and configuring them to monitor the respective RabbitMQ processes.
References
New to ADSelfService Plus?
Related Articles
Uninstrumented Block of Code - APM Insight
In the traces tab --> Slowest Method Calls and Count we show if you find Un-instrumented block of code the reason is as follows: Basically, What is un-instrumented block of code in APM Insight? By default, APM Insight agent monitors known frameworks ...Upgrade guide for OpManager v 12.7 and APM Plugin
After downloading the service pack for OpManager and the compatible service pack for Applications Manager Plugin (APM Plugin) to OpManager installed server, start the upgrade process for OpManager and APM Plugin by following the steps below: Note: If ...Monitoring HAProxy - Configuring the HAProxy Stats page
To monitor a HAProxy instance: Open the 'stats' port for collecting the metrics. To enable metrics collection, add the following content at the bottom of the file /etc/haproxy/haproxy.cfg: listen stats :9000 mode http stats enable stats hide-version ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...How to rename an existing APM - Java agent application's monitor?
In Applications Manager's APM(Application Performance Monitoring) doesn't support renaming applications/monitors from the web client. However, the application name of an existing application instance can be renamed in the `apminsight.conf` file and ...