/
Monitoring Service Check: rabbitmq_connections

Welcome to the VSHN Knowledge Base

Monitoring Service Check: rabbitmq_connections

Overview

This check monitors the number of established connections, connections that are not in state running and also their throughput.

Technical Details

Implementation

Global base checkNo
Puppet profiles using this checkprofile_rabbitmq

Check plugins

Namecheck_rabbitmq_connections
Packagesnagios-plugins-rabbitmq-vshn
CheckCommand namerabbitmq_connections
Upstream source linkhttps://git.vshn.net/vshn/nagios-plugins-rabbitmq-vshn
Documentation linkhttps://git.vshn.net/vshn/nagios-plugins-rabbitmq-vshn/blob/master/check_rabbitmq_connections

List of variables

Icinga2 variableConfigured inDefault ValueDescription
rabbitmq_conn_warn(not set)

The warning levels for each count of connections established, connections in a non-running state (flow, blocked), receive rate and send rate.  This field consists of one to four comma-separated thresholds.  Specify -1 if no threshold for a particular count.

rabbitmq_conn_crit(not set)

The critical levels for each count of connections established, connections in a non-running state (flow, blocked), receive rate and send rate. This field consists of one to four comma-separated thresholds.  Specify -1 if no threshold for a particular count.

rabbitmq_host
(not set) / requiredThe hostname to connect to
rabbitmq_username
guestThe user to connect as
rabbitmq_password
guest

The password for the user

rabbitmq_management_port
15672The management API port to connect to
rabbitmq_ssl
falseIf connection should use ssl to connect to the API


Troubleshooting/Known issues

Critical non running connections

This is a symptom of a rabbitmq nearing or even exceeding other thresholds like memory or disk usage. If you encounter this, please check memory and disk usage on the hosts. This could by caused by some clients overloading the cluster for example.

Solution

Tuning