Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
A set of nagios checks for RabbitMQ using the management interface
Perl

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
scripts
Build.PL
LICENSE.txt
MANIFEST
MANIFEST.SKIP
META.yml
Makefile
README.md
nagios-plugins-rabbitmq.spec

README.md

nagios-plugins-rabbitmq

Overview

This package contains a set of nagios checks useful for monitoring a RabbitMQ server. They use the RabbitMQ management interface with is 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.

Status

Currently we have 4 checks:

  • check_rabbitmq_aliveness

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

    • Use the /api/nodes API to gather resource usage of the rabbitmq server node
  • 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

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.

Author

James Casey jamesc.000@gmail.com

Something went wrong with that request. Please try again.