RabbitMQ plugin

Warning: The RabbitMQ plugin is deprecated. For more information, refer to Google Cloud's operations suite deprecations. For continued support for RabbitMQ, migrate to the solution provided by Blue Medora, or look at the complete list of Blue Medora BindPlane Sources.

RabbitMQ is an open source, complete and highly reliable enterprise messaging system based on the AMQP standard. For more information visit rabbitmq.com.

This functionality is only available for agents running on Linux. It is not available on Windows.

Discovery

Even if the RabbitMQ plugin is not configured, Monitoring discovers RabbitMQ services running in your Google Cloud project by:

• Searching instance names for rabbit or rabbitmq
• Checking for ports opened to 5672 via firewall rules

The services discovered are displayed on the RabbitMQ Services page in the Resources menu. After you install the monitoring agent and configure the RabbitMQ plugin on your instances, Monitoring populates the RabbitMQ Services page with inventory and metrics.

Configuring Monitoring to monitor RabbitMQ

After you install the monitoring agent, use the following instructions to configure the RabbitMQ plugin on your instances.

Prerequisites

The RabbitMQ plugin requires version 5.5.0-315 or later of the monitoring agent. To update the agent, see Upgrading the agent.

Enabling the RabbitMQ monitoring plugin

RabbitMQ is configured per queue on your system. At the moment, no drop-in configuration is available. The following configuration file shows how to configure one queue, named QUEUE_NAME.

On your VM instance, download rabbitmq.conf from the GitHub configuration repository and place it in the directory /etc/stackdriver/collectd.d/:

(cd /etc/stackdriver/collectd.d/ && sudo curl -O https://raw.githubusercontent.com/Stackdriver/stackdriver-agent-service-configs/master/etc/collectd.d/rabbitmq.conf)

As root, edit the downloaded configuration file and add information about your queues. Inline comments point out where you need to add configuration for additional queues. Wherever you see QUEUE_NAME, substitute the name of your queue.

After editing the configuration file, restart the monitoring agent by running the following command:

sudo service stackdriver-agent restart

For more information on the collectd curl_json plugin used to monitor RabbitMQ, see Plugin:cURL-JSON.

What is monitored

The full list of metrics the RabbitMQ plugin monitors is at Agent metrics: rabbitmq.