| Alert Name |
Alert Description |
Trigger Type (Critical / Warning) |
Alert Condition |
Recover Condition |
| RabbitMQ - High Memory Usage |
This alert fires when memory usage on a node in a RabbitMQ cluster is high. |
Critical |
> = 80 |
< 80 |
| RabbitMQ - No Consumers |
This alert fires when a RabbitMQ queue has no consumers. |
Critical |
< 1 |
> = 1 |
| RabbitMQ - High Disk Usage |
This alert fires when there is high disk usage on a node in a RabbitMQ cluster. |
Critical |
> = 80 |
< 80 |
| RabbitMQ - High Number of File Descriptors in use |
This alert fires when the percentage of file descriptors used by a node in a RabbitMQ cluster is high. |
Critical |
> = 90 |
< 90 |
| RabbitMQ - Node Down |
This alert fires when a node in the RabbitMQ cluster is down. |
Critical |
> = 1 |
< 1 |
| RabbitMQ - Too Many Connections |
This alert fires when there are too many connections to a node in a RabbitMQ cluster. |
Critical |
> = 1000 |
< 1000 |
| RabbitMQ - Too Many Un-acknowledged Messages |
This alert fires when we detect that there are too many un-acknowledged messages on a node in a RabbitMQ cluster. |
Critical |
> = 1000 |
< 1000 |
| RabbitMQ - Un-routable Messages |
This alert fires when we detect that a node in the RabbitMQ cluster has un-routable messages |
Critical |
> = 1 |
< 1 |
})
The RabbitMQ app is a unified logs and metrics app that helps you monitor the availability, performance, health, and resource utilization of your RabbitMQ messaging clusters. Preconfigured dashboards provide insight into cluster status, exchanges, queues, nodes and error logs.
## Sample log messages
})
The first service in the metrics pipeline is Telegraf. Telegraf collects metrics from RabbitMQ. Note that we’re running Telegraf in each pod we want to collect metrics from as a sidecar deployment for example, Telegraf runs in the same pod as the containers it monitors. Telegraf uses the RabbitMQ input plugin to obtain metrics. (For simplicity, the diagram doesn’t show the input plugins.) The injection of the Telegraf sidecar container is done by the Telegraf Operator. Prometheus pulls metrics from Telegraf and sends them to [Sumo Logic Distribution for OpenTelemetry Collector](https://github.com/SumoLogic/sumologic-otel-collector) which enriches metadata and sends metrics to Sumo Logic.
In the logs pipeline, Sumo Logic Distribution for OpenTelemetry Collector collects logs written to standard out and forwards them to another instance of Sumo Logic Distribution for OpenTelemetry Collector, which enriches metadata and sends logs to Sumo Logic.
:::note Prerequisites
It’s assumed that you are using the latest helm chart version. If not, upgrade using the instructions [here](/docs/send-data/kubernetes).
:::
#### Configure Metrics Collection
This section explains the steps to collect RabbitMQ metrics from a Kubernetes environment.
In Kubernetes environments, we use the Telegraf Operator, which is packaged with our Kubernetes collection. You can learn more on this[ here](/docs/send-data/collect-from-other-data-sources/collect-metrics-telegraf/telegraf-collection-architecture). Follow the steps listed below to collect metrics from a Kubernetes environment:
1. [Set up Kubernetes Collection with the Telegraf Operator](/docs/send-data/collect-from-other-data-sources/collect-metrics-telegraf/install-telegraf)
2. On your RabbitMQ Pods, add the following annotations:
```sql
annotations:
telegraf.influxdata.com/class: sumologic-prometheus
prometheus.io/scrape: "true"
prometheus.io/port: "9273"
telegraf.influxdata.com/inputs: |+
[[inputs.rabbitmq]]
url = "http://localhost:15672"
username = "})
### Node
The RabbitMQ - Node dashboard helps you Get an at-a-glance view of the state of the nodes in the RabbitMQ cluster.
Use this dashboard to:
* Monitor the number of open file descriptors.
* Monitor uptime of nodes.
* Determine the amount of ram transaction, disk transaction.
* Determine the amount of garbage collection per second.
* Monitor current memory usage
})
### Queue
The RabbitMQ - Queue dashboard provides an at-a-glance view of the state of your queues in your RabbitMQ clusters.
Use this dashboard to:
* Monitor number of consumers on queues
* Gain insights into pushing messages rate for queues of your RabbitMQ cluster.
* Gain insights into delivery messages rate for queues of your RabbitMQ cluster.
* Determine the amount of slave nodes for queues.
* Monitor memory usage of queues over time.
* Determine the number of error messages on queues.
})
### Exchanges
The RabbitMQ - Exchanges dashboard provides an at-a-glance view of the state of your exchanges in your RabbitMQ clusters.
Use this dashboard to:
* Monitor number of total messages published in exchanges
* Monitor number of total messages published out exchanges
* Gain insights into message publish Rate in exchanges of your RabbitMQ cluster.
* Gain insights into message publish Rate out exchanges of your RabbitMQ cluster.
})
### Logs
This dashboard helps you quickly analyze your RabbitMQ error logs across all clusters.
Use this dashboard to:
* Identify critical events in your RabbitMQ cluster.
* Examine trends to detect spikes in Error or Fatal events
* Monitor Broker added/started and shutdown events in your cluster.
* Quickly determine patterns across all logs in a given RabbitMQ cluster.
})
## Create monitors for RabbitMQ app
import CreateMonitors from '../../reuse/apps/create-monitors.md';