CHECK_R...OBJECTS(1p)
β¨ NAME β¨
ok so check_rabbitmq_objects is a Nagios plugin that uses the RabbitMQ management API to count how many of the various broker objects are out there π
it's a 1p manpage from the User Contributed Perl Documentation corner of the world, and it's lowkey iconic
π° SYNOPSIS π°
check_rabbitmq_objects [options] -H hostname
like, you give it options, you give it a host, and it goes off π«Ά
πΈ DESCRIPTION πΈ
bestie, the whole vibe here is: poke the management interface of RabbitMQ and count how many of various broker objects exist. Then those counts get published as performance metrics for the check. slay β¨
rn the objects it counts are:
vhostexchangebindingqueuechannel
It uses Monitoring::Plugin, which means it accepts all the standard Nagios options β no cap π
π OPTIONS π
-h|--helpβ shows you the help text, because we all need a lil guidance sometimes π-v|--verboseβ verbose output, for when you want the β¨full teaβ¨-t|--timeoutβ set a timeout for the check, in seconds β±οΈ-H|--hostname|--hostβ the host to connect to--portβ the port to connect to (default:55672)--sslβ use SSL when connecting (default:false)--username|--userβ the user to connect as (default:guest)--passβ the password for the user (default:guest)
okay but notice how--hostnameand--hostare the same thing, and--usernameand--userare the same thing. twin energy fr fr π―
π¦ EXAMPLES π¦
the defaults all work with a standard fresh install of RabbitMQ, and literally all you need to specify is the host to connect to:
check_rabbitmq_objects -H rabbit.example.com
and it gives you back a standard Nagios result, no notes:
RABBITMQ_OBJECTS OK - Gathered Object Counts | vhost=1;; exchange=7;;
binding=2;; queue=1;; channel=0;;
ate that π
π ERRORS π
the check tries to be helpful and give you useful error messages on the status line for standard error conditions. it's doing its best okay π
otherwise, it just returns the HTTP Error message that the management interface handed back. raw and unfiltered, as it should be.
π₯ EXIT STATUS π₯
returns zero if the check is OK. otherwise it returns the standard Nagios exit codes to signify WARNING, UNKNOWN or CRITICAL state.
so like, 0 = we're so back, anything else = it's giving problems π¨
π SEE ALSO π
- see
Monitoring::Plugin(3) - the RabbitMQ management plugin is described at
http://www.rabbitmq.com/management.html
iykyk π
π LICENSE π
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.
fr fr, read the license, it's not that long bestie π«Ά
π§ AUTHOR π§
James Casey <jamesc.000@gmail.com>
and that's the whole page!! this lil cutie was written by perl v5.40.1, dated 2026-01-26, and it lives at CHECK_R...OBJECTS(1p) π main character energy, honestly. bye bestie, go count some broker objects πΈπ¦β¨
π¦ where this page comes from
- ubuntu resolute: nagios-plugins-rabbitmq 1:1.2.0-2.5ubuntu2
- ubuntu stonking: nagios-plugins-rabbitmq 1:1.2.0-2.5ubuntu2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms