nagios-plugins-rabbitmq

  

Overview

This package contains a set of nagios checks useful for monitoring a RabbitMQ server. They use the RabbitMQ management interface over HTTP and therefore have a very light profile on the Nagios server.

See the documentation on the RabbitMQ management interface for more details on what it provides.

Branches

• master - Default and development branch which use Monitoring::plugin . All pull request are merged on this branch and tested before any merging or backporting to other branches
• libperl-monitoring-plugin - Stable branche which use the perl Monitoring::plugin
• libperl-nagios-plugin - Stable branche which use the perl Nagios::plugin

NOTE: The perl Nagios::plugin is now deprecated and renamed into Monitoring::plugin. It's explained here.

Nagios::Plugin - Removed from CPAN by request of Nagios Enterprises, succeeded by Monitoring::Plugin

Status

Currently we have the following checks:

• check_rabbitmq_aliveness

  • Use the /api/aliveness-test API to send/receive a message.

• check_rabbitmq_connections

  • Use the /api/connections API to gather details of connections used, their state and their throughput

• check_rabbitmq_exchange

  • Use the /api/exchanges API to collect average rates of confirmed, published in and published out messages/second in a period of time on a given exchange.

• check_rabbitmq_objects

  • Use a variety of APIs to count instances of various objects on the server. These include vhosts, exchanges, bindings, queues and channels.

• check_rabbitmq_overview

  • Use the /api/overview API to collect the number of pending, ready and unacknowledged messages on the server

• check_rabbitmq_partition

  • Use the /api/nodes API to check for partitions in a RabbitMQ cluster.

• check_rabbitmq_cluster

  • Use the /api/nodes API to check how many node are alive in the cluster.

• check_rabbitmq_queue

  • Use the /api/queue API to collect the number of pending, ready and unacknowledged messages and the number of consumers on a given queue or all the queues available. Exclude parameter also works if all queues are checked

• check_rabbitmq_server

  • Use the /api/nodes API to gather resource usage of the rabbitmq server node

• check_rabbitmq_shovels

  • Use the /api/nodes API check that all the shovels of the given RabbitMQ host are running

• check_rabbitmq_watermark

  • Use the /api/nodes API to check to see if mem_alarm has been set to true

See the relevant POD documentation/man pages for more information on usage.

Licence

This file is part of nagios-plugins-rabbitmq.

Copyright 2010, Platform 14.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Contributors

James Casey jamesc.000@gmail.com, Thierno IB. BARRY @barryib