-
Notifications
You must be signed in to change notification settings - Fork 384
collectors RabbitMQCollector
Rob Smith edited this page Apr 30, 2014
·
14 revisions
Collects data from RabbitMQ through the admin interface
** With added support for breaking down queue metrics by vhost, we have attempted to keep results generated by existing configurations from changing. This means that the old behaviour of clobbering queue metrics when a single queue name exists in multiple vhosts still exists if the configuration is not updated. If no vhosts block is defined it will also keep the metric path as it was historically with no vhost name in it.
old path => systems.myServer.rabbitmq.queues.myQueue.*
new path => systems.myServer.rabbitmq.myVhost.queues.myQueue.*
** If a [vhosts] section exists but is empty, then no queues will be polled. ** To poll all vhosts and all queues, add the following. ** [vhosts] ** * = * **
- pyrabbit
Options - Generic Options
Setting | Default | Description | Type |
---|---|---|---|
byte_unit | byte | Default numeric output(s) | str |
enabled | False | Enable collecting these metrics | bool |
host | localhost:55672 | Hostname and port to collect from | str |
measure_collector_time | False | Collect the collector run time in ms | bool |
password | guest | Password | str |
queues | Queues to publish. Leave empty to publish all. | ||
user | guest | Username | str |
vhosts | A list of vhosts and queues for which we want to collect |
servers.hostname.rabbitmq.key 4
servers.hostname.rabbitmq.more_keys.nested_key 3
servers.hostname.rabbitmq.queues.test_queue.key 2
servers.hostname.rabbitmq.queues.test_queue.more_keys.nested_key 1