CHECK_R...TERMARK(1p)
π NAME π
okay bestie, gather round β this is check_rabbitmq_watermark, a Nagios plugin that uses the RabbitMQ management API to check whether the mem_alarm or disk_free_alarm has been triggered. like, is your rabbit okay or is it screaming? that's the whole job. π°β¨
(it lives in section 1p of the perl manual pages, iykyk.)
β¨ SYNOPSIS β¨
check_rabbitmq_watermark [options] -H hostname
that's it. that's the vibe. π
π¦ DESCRIPTION π¦
so the way this works: it uses the management interface of RabbitMQ to check if the mem_alarm or disk_free_alarm has been triggered. no cap, that's literally the entire mission statement.
it uses Monitoring::Plugin and accepts all standard Nagios options. so if you already know Nagios options, you're basically home. π
πΈ OPTIONS πΈ
-h|--helpβ display the help text, bestie. like when you're lost, ask for help, it's iconic π-v|--verboseβ verbose output. more words. more info. we love a chatty flag π£οΈ-t|--timeoutβ set a timeout for the check, in seconds β±οΈ-H|--hostname|--hostβ the host to connect to. this is the one you gotta give it π«Ά--portβ the port to connect to (default:55672)--sslβ use SSL when connecting (default:false). glow up your connection π--vhostβ the vhost to create the test queue within (default:/)-n|--nodeβ the node name (default ishostname)--username|--userβ the user to connect as (default:guest)--passβ the password for the user (default:guest)
ngl theguest/guestdefault is giving "default credentials" energy, which is exactly why it works on a fresh install. π
π EXAMPLES π
the defaults all work with a standard fresh install of RabbitMQ, and all that is needed is to specify the host to connect to:
check_rabbitmq_watermark -H rabbit.example.com
this returns a standard Nagios result:
RABBITMQ_ALIVENESS OK - vhost: /
you can choose a different vhost to use for the check also:
check_rabbitmq_watermark -H rabbit.example.com --vhost /foo
look at her go. π₯
π ERRORS π
the check tries to provide useful error messages on the status line for standard error conditions. so it won't leave you on read. π
otherwise, it returns the HTTP Error message returned by the management interface.
π EXIT STATUS π
returns zero if the check is OK β otherwise returns standard Nagios exit codes to signify WARNING, UNKNOWN or CRITICAL state. so the exit code is the whole mood ring basically. π
π SEE ALSO π
- see
Monitoring::Plugin(3) - the RabbitMQ management plugin is described at
http://www.rabbitmq.com/management.html
π 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.
π«Ά AUTHOR π«Ά
James Casey <jamesc.000@gmail.com>
okay that's the whole page, no notes. this gem is from perl v5.40.1, dated 2026-01-26, and the manpage goes by CHECK_R...TERMARK(1p) if you're searching for her. periodt. π
β¨
π¦ 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