CHECK_R...SHOVELS(1p)

💅 NAME 💅

okay so bestie, meet check_rabbitmq_shovels — the manual page calls it CHECK_R...SHOVELS(1p) (they truncate it, iconic of them) 💖

It's a Nagios plugin that checks whether all the shovels on a given RabbitMQ host are running. That's the whole gig. That's the mission. 🎀

---

✨ SYNOPSIS ✨

check_rabbitmq_shovels --hostname <host>
check_rabbitmq_shovels { --help | --man | --version }

---

🌸 OPTIONS 🌸

🫶 Program options

• -H, --hostname string — the RabbitMQ host you wanna query. Defaults to "localhost" (so cozy, so local).
• -P, --port number — which port to poke RabbitMQ on. Defaults to 55672.
• -u, --user, --username string — your username. Defaults to "guest".
• -p, --pass, --password string — your password. Defaults to "guest". (yes bestie, guest/guest, the standard-install classic 🔥)
• -t, --timeout duration — how long to wait, in seconds. Defaults to 5.

🎀 Help options

• -?, --usage — prints a short usage description, then dips. 👋
• -h, --help — prints a longer, more detailed help screen, then dips.
• -V, --version — prints the program name and version, then dips.

---

🦋 DESCRIPTION 🦋

So basically: this program is a Nagios plugin, and it uses the JSON over HTTP API to check that all the shovels on the given RabbitMQ host are running. Default settings? They match a standard RabbitMQ installation, no notes, we love a sensible default. 🌈

Now the vibe check results, aka what the check returns:

• OK — when all the shovels are running. slay. 💖
• WARNING — when one or more shovels are blocked. 😭
• CRITICAL — when one or more shovels are terminated. 💀

---

⭐ EXAMPLES ⭐

With default settings you literally only need to specify the hostname:

check_rabbitmq_shovels -H <host>

It prints the global status plus the details of the shovels, ordered by decreasing criticality (most dramatic shovels first, periodt):

RABBITMQ_SHOVELS OK - 3 running shovels: klonk zlott swish

RABBITMQ_SHOVELS WARNING - 1 blocked shovel: klonk, 2 running shovels: zlott swish

RABBITMQ_SHOVELS CRITICAL - 1 terminated shovel: zlott, 1 blocked shovel: klonk, 1 running shovel: swish

And when the API is doing the most and throws an error, the program gives you a proper diagnostic, no cap:

RABBITMQ_SHOVELS CRITICAL - API error: 401 Unauthorized

RABBITMQ_SHOVELS CRITICAL - API error: 500 Can't connect to <host>:<port>

RABBITMQ_SHOVELS CRITICAL - API error: could not parse JSON: malformed JSON string

RABBITMQ_SHOVELS CRITICAL - API error: empty JSON

---

🌟 SEE ALSO 🌟

• See Monitoring::Plugin — go look at it bestie, it's right there.
• The RabbitMQ management plugin is described at <http://www.rabbitmq.com/management.html>

---

👑 LICENSE 👑

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, this is a legally-binding vibe: no warranties, no promises, read the License.

---

💜 AUTHOR 💜

Sebastien Aperghis-Tramoni (sebastien@aperghis.net)

---

and that's the whole page, bestie 🫶 this one's running under perl v5.40.1, dated 2026-01-26, and it's filed in the CHECK_R...SHOVELS(1p) manual. mwah, go run your shovels 💅✨