---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# RabbitMQ default checks and policies

# RabbitMQ default checks and policies {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of RabbitMQ default checks and policies

ServiceNow's Agent Client Collector includes a comprehensive set of default checks and policies to monitor the health of RabbitMQ servers.
These checks require prior RabbitMQ discovery and are specifically available in Windows environments.
They enable proactive monitoring by verifying server status, cluster health, message queues, and more, sending alerts when issues arise.
Show full answer Show less  

## Key Features

* **Health and Availability Checks:** Commands like `check-rabbitmq-alive` and `check-rabbitmq-node-health` confirm if the RabbitMQ server and its nodes are running properly, triggering alerts if they are down or in an unhealthy state.
* **Cluster and Network Monitoring:** The `check-rabbitmq-cluster-health` and `check-rabbitmq-network-partitions` checks monitor cluster node status and detect network partitions that could impact service availability.
* **Queue and Consumer Metrics:** Checks such as `check-rabbitmq-consumers`, `check-rabbitmq-messages`, and `check-rabbitmq-queue-drain-time` monitor queue depth, consumer counts, and message drain times to identify potential bottlenecks or overloads.
* **Resource Usage Monitoring:** The `check-rabbitmq-node-usage` provides insights into node resource consumption including memory, disk, file descriptors, sockets, and processes.
* **Queue Synchronization:** The `check-rabbitmq-queues-synchronised` check ensures that mirrored queues are properly synchronized, which is critical for data consistency.
* **Protocol-Specific Health:** The `check-rabbitmq-stomp-alive` verifies RabbitMQ responsiveness via the STOMP protocol.
* **Metrics Collection:** Metric policies like `metrics-rabbitmq-overview` and `metrics-rabbitmq-queue` gather statistical data about the overall RabbitMQ environment and individual queues, supporting performance analysis and capacity planning.

## Practical Use and Benefits

By leveraging these default checks and policies, ServiceNow customers can:

* Ensure continuous RabbitMQ server availability and promptly detect outages or degraded performance.
* Gain visibility into cluster health and network issues to minimize downtime risks.
* Monitor message flow and queue health to prevent processing delays and message backlogs.
* Track resource utilization to optimize RabbitMQ node performance and plan capacity.
* Receive alerts based on configurable thresholds tailored to their operational requirements.
* Access detailed metrics for informed troubleshooting and performance tuning.

All commands support customizable parameters such as host, port, virtual host, warning, and critical thresholds, allowing precise monitoring aligned with the customer's RabbitMQ deployment.  
Agent Client Collector provides the following default checks and
policies for RabbitMQ health monitoring. You must perform RabbitMQ discovery before executing
the checks. RabbitMQ checks are available only in a Windows
environment.
{#rabbitmq-checks-policies__table_lsp_hsb_3tb__entry__4}

| Type | Check | Description | Command |
|-|-|-|-|
| Event | check-rabbitmq-alive | Verifies whether the RabbitMQ server is alive, using the REST API. If the server is down, an alert triggers. | `check-rabbitmq-alive.rb --host {{.labels.params_host}} --port {{.labels.params_port}} -v {{.labels.params_vhost}}` |
| Event | check-rabbitmq-cluster-health | Verifies whether the RabbitMQ server's cluster nodes are running. If the nodes are down, an alert triggers. | `check-rabbitmq-cluster-health.rb --host {{.labels.params_host}} --port {{.labels.params_port}}` |
| Event | check-rabbitmq-consumers | Verifies the number of consumers on the RabbitMQ server and triggers an alert based on the configured threshold. | `check-rabbitmq-consumers.rb {{if .labels.params_warn}} --warn {{.labels.params_warn}} {{end}} {{if .labels.params_critical}} --critical {{.labels.params_critical}} {{end}} --host {{.labels.params_host}} --port {{.labels.params_port}}` |
| Event | check-rabbitmq-messages | Verifies the total number of messages queued on the RabbitMQ server and triggers an alert based on the threshold. | `check-rabbitmq-messages.rb --critical {{.labels.params_critical}} --port {{.labels.params_port}} --warn {{.labels.params_warn}} --host {{.labels.params_host}}` |
| Event | check-rabbitmq-network-partitions | Verifies whether the RabbitMQ network partition has occurred and triggers an alert based on the threshold. | check-rabbitmq-network-partitions.rb --host {{.labels.params_host}} --port {{.labels.params_port}} |
| Event | check-rabbitmq-node-health | Verifies whether the RabbitMQ server node is in a running state. | check-rabbitmq-node-health.rb --host {{.labels.params_host}} {{if .labels.params_watchalarms}} --alarms {{.labels.params_watchalarms}} {{end}} {{if .labels.params_socketwarn}} --swarn {{.labels.params_socketwarn}} {{end}} {{if .labels.params_memcrit}} --mcrit {{.labels.params_memcrit}} {{end}} {{if .labels.params_fdcrit}} --fcrit {{.labels.params_fdcrit}} {{end}} {{if .labels.params_socketcrit}} --scrit {{.labels.params_socketcrit}} {{end}} --port {{.labels.params_port}} {{if .labels.params_memwarn}} --mwarn {{.labels.params_memwarn}} {{end}} {{if .labels.params_fdwarn}} --fwarn {{.labels.params_fdwarn}} {{end}} |
| Event | check-rabbitmq-node-usage | Checks and displays usage of the RabbitMQ server node. | check-rabbitmq-node-usage.rb {{if .labels.params_procwarn}} --pwarn {{.labels.params_procwarn}} {{end}} --port {{.labels.params_port}} {{if .labels.params_socketwarn}} --swarn {{.labels.params_socketwarn}} {{end}} --type {{.labels.params_type}} {{if .labels.params_diskcrit}} --dcrit {{.labels.params_diskcrit}} {{end}} {{if .labels.params_fdcrit}} --fcrit {{.labels.params_fdcrit}} {{end}} {{if .labels.params_proccrit}} --pcrit {{.labels.params_proccrit}} {{end}} {{if .labels.params_diskwarn}} --dwarn {{.labels.params_diskwarn}} {{end}} {{if .labels.params_socketcrit}} --scrit {{.labels.params_socketcrit}} {{end}} --host {{.labels.params_host}} {{if .labels.params_memcrit}} --mcrit {{.labels.params_memcrit}} {{end}} {{if .labels.params_fdwarn}} --fwarn {{.labels.params_fdwarn}} {{end}} {{if .labels.params_memwarn}} mwarn {{.labels.params_memwarn}} {{end}} |
| Event | check-rabbitmq-queue-drain-time | Verifies the time it will take for each queue on the RabbitMQ server to drain, based on the current message exit rate. For example, if a queue has 1,000 messages in it but only 1 message exits per second, an alert generates. The default critical level of 360 seconds has been exceeded. | `check-rabbitmq-queue-drain-time.rb --host {{.labels.params_host}} --port {{.labels.params_port}} --warn {{.labels.params_warn}} --critical {{.labels.params_critical}}` |
| Event | check-rabbitmq-queues-synchronised | Verifies that all mirrored queues with secondary queues are synchronised. | `check-rabbitmq-queues-synchronised.rb --host {{.labels.params_host}} --port {{.labels.params_port}}` |
| Event | check-rabbitmq-stomp-alive | Verifies whether the RabbitMQ server is alive and responding to STOMP. | `check-rabbitmq-stomp-alive.rb --host {{.labels.params_host}} --queue {{.labels.params_queue}} --port {{.labels.params_port}}` |
[Table 1. RabbitMQ Events policy]

{#rabbitmq-checks-policies__table_lsp_hsb_3tb} {#rabbitmq-checks-policies__table_rw5_xzb_3tb__entry__4}

| Type | Check | Description | Command |
|-|-|-|-|
| Metric | metrics-rabbitmq-overview | Provides RabbitMQ overview statistics. | `metrics-rabbitmq-overview.rb --port {{.labels.params_port}} --host {{.labels.params_host}}` |
| Metric | metrics-rabbitmq-queue | Provides RabbitMQ metrics per queue. | `metrics-rabbitmq-queue.rb --port {{.labels.params_port}} --host {{.labels.params_host}} {{if .labels.params_vhost}} --vhost {{.labels.params_vhost}} {{end}}` |
[Table 2. RabbitMQ Metrics policy]

{#rabbitmq-checks-policies__table_rw5_xzb_3tb}