Sensu-Plugins-rabbitmq
Sensu Asset
The Sensu assets packaged from this repository are built against the Sensu Ruby runtime environment. When using these assets as part of a Sensu Go resource (check, mutator or handler), make sure you include the corresponding Sensu Ruby runtime asset in the list of assets needed by the resource. The current ruby-runtime assets can be found here in the Bonsai Asset Index.
Functionality
Files
- bin/check-rabbitmq-alive.rb
- bin/check-rabbitmq-amqp-alive.rb
- bin/check-rabbitmq-cluster-health.rb
- bin/check-rabbitmq-consumers.rb
- bin/check-rabbitmq-consumer-utilisation.rb
- bin/check-rabbitmq-messages.rb
- bin/check-rabbitmq-network-partitions.rb
- bin/check-rabbitmq-node-health.rb
- bin/check-rabbitmq-node-usage.rb
- bin/check-rabbitmq-queue-drain-time.rb
- bin/check-rabbitmq-queue.rb
- bin/check-rabbitmq-queues-synchronised.rb
- bin/check-rabbitmq-stomp-alive.rb
- bin/metrics-rabbitmq-overview.rb
- bin/metrics-rabbitmq-queue.rb
- bin/metrics-rabbitmq-exchange.rb
Usage
Installation
Permissions
In order to run these checks you need the following permissions set:
:conf => '^aliveness-test$',
:write => '^amq\.default$',
:read => '.*'
You must also add the monitoring tag.
This can be done like this:
rabbitmqctl add_user sensu_monitoring $MY_SUPER_LONG_SECURE_PASSWORD
rabbitmqctl set_permissions -p / sensu_monitoring "^aliveness-test$" "^amq\.default$" "^(amq\.default|aliveness-test)$"
rabbitmqctl set_user_tags sensu_monitoring monitoring
It is highly recommended that you do not give administrator access! and use minimum permissions!