kbudde/rabbitmq-exporter

By kbudde

Updated over 2 years ago

rabbitmq_exporter for prometheus

Image
20

50M+

kbudde/rabbitmq-exporter repository overview

RabbitMQ Exporter Build Status Coverage Status

Prometheus exporter for RabbitMQ metrics. Data is scraped by prometheus.

Please note this an unofficial plugin. There is also an official plugin from RabbitMQ.com. See comparison to official exporter

Installation

Binary release

You can download the latest release on the release page. Configuration is done with environment variables. See below.

docker: rabbitmq container with network sharing

The rabbitmq_exporter is sharing the network interface with the rabbitmq container -> it is possible to use localhost and default user/password (guest).

  1. Start rabbitMQ

     docker run -d -e RABBITMQ_NODENAME=my-rabbit --name my-rabbit -p 9419:9419 rabbitmq:3-management
    
  2. Start rabbitmq_exporter in container.

     docker run -d --net=container:my-rabbit kbudde/rabbitmq-exporter
    

Now your metrics are exposed through http://host:9419/metrics. The management plugin does not need to be exposed.

Configuration

Rabbitmq_exporter can be configured using json config file or environment variables for configuration.

Config file

Rabbitmq_exporter expects config file in "conf/rabbitmq.conf". If the file is found it is used as configuration source. The name of the file can be overriden with flag:

./rabbitmq_exporter -config-file config.example.json

You can find an example here.

Settings
Environment variabledefaultdescription
RABBIT_URLhttp://127.0.0.1:15672url to rabbitMQ management plugin (must start with http(s)://)
RABBIT_USERguestusername for rabbitMQ management plugin. User needs monitoring tag!
RABBIT_PASSWORDguestpassword for rabbitMQ management plugin
RABBIT_USER_FILElocation of file with username (useful for docker secrets)
RABBIT_PASSWORD_FILElocation of file with password (useful for docker secrets)
PUBLISH_PORT9419Listening port for the exporter
PUBLISH_ADDR""Listening host/IP for the exporter
OUTPUT_FORMATTTYLog ouput format. TTY and JSON are suported
LOG_LEVELinfolog level. possible values: "debug", "info", "warning", "error", "fatal", or "panic"
CAFILEca.pempath to root certificate for access management plugin. Just needed if self signed certificate is used. Will be ignored if the file does not exist
CERTFILEclient-cert.pempath to client certificate used to verify the exporter's authenticity. Will be ignored if the file does not exist
KEYFILEclient-key.pempath to private key used with certificate to verify the exporter's authenticity. Will be ignored if the file does not exist
SKIPVERIFYfalsetrue/0 will ignore certificate errors of the management plugin
SKIP_VHOST^$regex, matching vhost names are not exported. First performs INCLUDE_VHOST, then SKIP_VHOST
INCLUDE_VHOST.*regex vhost filter. Only queues in matching vhosts are exported
INCLUDE_QUEUES.*regex queue filter. Just matching names are exported
SKIP_QUEUES^$regex, matching queue names are not exported (useful for short-lived rpc queues). First performed INCLUDE, after SKIP
RABBIT_CAPABILITIESbert,no_sortcomma-separated list of extended scraping capabilities supported by the target RabbitMQ server
RABBIT_EXPORTERSexchange,node,queueList of enabled modules. Possible modules: connections,shovel,federation,exchange,node,queue,memory
RABBIT_TIMEOUT30timeout in seconds for retrieving data from management plugin.
MAX_QUEUES0max number of queues before we drop metrics (disabled if set to 0)
EXCLUDE_METRICSMetric names to exclude from export. comma-seperated. e.g. "recv_oct, recv_cnt". See exporter_*.go for names

Example and recommended settings:

SKIP_QUEUES="RPC_.*" MAX_QUEUES=5000 ./rabbitmq_exporter
Extended RabbitMQ capabilities

Newer version of RabbitMQ can provide some features that reduce overhead imposed by scraping the data needed by this exporter. The following capabilities are currently supported in RABBIT_CAPABILITIES env var:

  • no_sort: By default RabbitMQ management plugin sorts results using the default sort order of vhost/name. This sorting overhead can be avoided by passing empty sort argument (?sort=) to RabbitMQ starting from version 3.6.8. This option can be safely enabled on earlier 3.6.X versions, but it'll not give any performance improvements. And it's incompatible with 3.4.X and 3.5.X.
  • bert: Since 3.6.9 (see https://github.com/rabbitmq/rabbitmq-management/pull/367) RabbitMQ supports BERT encoding as a JSON alternative. Given that BERT encoding is implemented in C inside the Erlang VM, it's way more effective than pure-Erlang JSON encoding. So this greatly reduces monitoring overhead when we have a lot of objects in RabbitMQ.

Note for users of rabbmitmq < 3.6

no_sort and bert are enabled by default. You must overwrite the default settings with:

RABBIT_CAPABILITIES=nobert ./rabbitmq_exporter

Metrics

All metrics (except golang/prometheus metrics) are prefixed with "rabbitmq_".

Global

Always exported.

metricdescription
upWas the last scrape of rabbitmq successful.
module_upWas the last scrape of rabbitmq module successful. labels: module
module_scrape_duration_secondsDuration of the last scrape of rabbitmq module. labels: module
exporter_build_infoA metric with a constant '1' value labeled by version, revision, branch and build date on which the rabbitmq_exporter was built.
Overview

Always exported. Labels: cluster

metricdescription
channelsNumber of channels
connectionsNumber of connections
consumersNumber of message consumers
queuesNumber of queues in use
exchangesNumber of exchanges in use
queue_messages_globalNumber ready and unacknowledged messages in cluster.
queue_messages_ready_globalNumber of messages ready to be delivered to clients.
queue_messages_unacknowledged_globalNumber of messages delivered to clients but not yet acknowledged.
version_infoA metric with a constant '1' value labeled by rabbitmq version, erlang version, node, cluster.
Queues

Labels: cluster, vhost, queue, durable, policy, self

Queues - Gauge
metricdescription
queue_messages_readyNumber of messages ready to be delivered to clients.
queue_messages_unacknowledgedNumber of messages delivered to clients but not yet acknowledged.
queue_messagesSum of ready and unacknowledged messages (queue depth).
queue_messages_ack_totalNumber of messages delivered in acknowledgement mode in response to basic.get.
queue_messages_ready_ramNumber of messages from messages_ready which are resident in ram.
queue_messages_unacknowledged_ramNumber of messages from messages_unacknowledged which are resident in ram.
queue_messages_ramTotal number of messages which are resident in ram.
queue_messages_persistentTotal number of persistent messages in the queue (will always be 0 for transient queues).
queue_message_bytesSum of the size of all message bodies in the queue. This does not include the message properties (including headers) or any overhead.
queue_message_bytes_readyLike message_bytes but counting only those messages ready to be delivered to clients.
queue_message_bytes_unacknowledgedLike message_bytes but counting only those messages delivered to clients but not yet acknowledged.
queue_message_bytes_ramLike message_bytes but counting only those messages which are in RAM.
queue_message_bytes_persistentLike message_bytes but counting only those messages which are persistent.
queue_consumersNumber of consumers.
queue_consumer_utilisationFraction of the time (between 0.0 and 1.0) that the queue is able to immediately deliver messages to consumers. This can be less than 1.0 if consumers are limited by network congestion or prefetch count.
queue_memoryBytes of memory consumed by the Erlang process associated with the queue, including stack, heap and internal structures.
queue_head_message_timestampThe timestamp property of the first message in the queue, if present. Timestamps of messages only appear when they are in the paged-in state.
queue_max_length_bytesTotal body size for ready messages a queue can contain before it starts to drop them from its head.
queue_max_lengthHow many (ready) messages a queue can contain before it starts to drop them from its head.
queue_idle_since_secondsstarttime where the queue switched to idle state; seconds since epoch (1970); only set if queue state is idle
queue_reductions_totalNumber of reductions which take place on this process.
queue_stateA metric with a value of constant '1' if the queue is in a certain state. Labels: vhost, queue, state (running, idle, flow,..)
queue_slave_nodes_lenNumber of slave nodes attached to the queue
queue_synchronised_slave_nodes_lenNumber of slave nodes in sync to the queue
Queues - Counter
metricdescription
queue_disk_reads_totalTotal number of times messages have been read from disk by this queue since it started.
queue_disk_writes_totalTotal number of times messages have been written to disk by this queue since it started.
queue_messages_published_totalCount of messages published.
queue_messages_confirmed_totalCount of messages confirmed.
queue_messages_delivered_totalCount of messages delivered in acknowledgement mode to consumers.
queue_messages_delivered_noack_totalCount of messages delivered in no-acknowledgement mode to consumers.
queue_messages_get_totalCount of messages delivered in acknowledgement mode in response to basic.get.
queue_messages_get_noack_totalCount of messages delivered in no-acknowledgement mode in response to basic.get.
queue_messages_redelivered_totalCount of subset of messages in deliver_get which had the redelivered flag set.
queue_messages_returned_totalCount of messages returned to publisher as unroutable.
Exchanges - Counter

Labels: cluster, vhost, exchange

metricdescription
exchange_messages_published_in_totalCount of messages published in to an exchange, i.e. not taking account of routing.
exchange_messages_published_out_totalCount of messages published out of an exchange, i.e. taking account of routing.
Node - Counter

Labels: cluster, node, self

metricdescription
uptimeUptime in milliseconds
runningnumber of running nodes
node_mem_usedMemory used in bytes
node_mem_limitPoint at which the memory alarm will go off
node_mem_alarmWhether the memory alarm has gone off
node_disk_freeDisk free space in bytes.
node_disk_free_alarmWhether the disk alarm has gone off.
node_disk_free_limitPoint at which the disk alarm will go off.
fd_usedUsed File descriptors
fd_availableFile descriptors available
sockets_usedFile descriptors used as sockets.
sockets_availableFile descriptors available for use as sockets
partitionsCurrent Number of network partitions. 0 is ok. If the cluster is splitted the value is at least 2
Connections - Gauge

disabled by default. Depending on the environment and change rate it can create a high number of dead metrics. Otherwise it could be usefull and can be enabled.

Labels: cluster, vhost, node, peer_host, user, self

Please note: The data is aggregated by label values as it is possible that there are multiple connections for a certain combination of labels.

metricdescription
connection_channelsnumber of channels in use
connection_received_bytesreceived bytes
connection_received_packetsreceived packets
connection_send_bytessend bytes
connection_send_packetssend packets
connection_send_pendingSend queue size

Labels: vhost, node, peer_host, user, state (running, flow,..), self

metricdescription
connection_statusNumber of connections in a certain state aggregated per label combination. Metric will disappear if there are no connections in a state.
Shovel

disabled by default Labels: cluster, vhost, shovel, type, self, state

metricdescription
shovel_stateA metric with a value of constant '1' for each shovel in a certain state
Memory

disabled by default Labels: cluster, node, self

metricdescription
memory_allocated_unused_bytesMemory preallocated by the runtime (VM allocators) but not yet used
memory_atom_bytesMemory used by atoms. Should be fairly constant
memory_binary_bytesMemory used by shared binary data in the runtime. Most of this memory is message bodies and metadata.)
memory_code_bytesMemory used by code (bytecode, module metadata). This section is usually fairly constant and relatively small (unless the node is entirely blank and stores no data).
memory_connection_channels_bytesMemory used by client connections - channels
memory_connection_other_bytesMemory used by client connection - other
memory_connection_readersMemory used by processes responsible for connection parser and most of connection state. Most of their memory attributes to TCP buffers
memory_connection_writers_bytesMemory used by processes responsible for serialization of outgoing protocol frames and writing to client connections socktes
memory_mgmt_db_bytesManagement DB ETS tables + processes
memory_mnesia_bytesInternal database (Mnesia) tables keep an in-memory copy of all its data (even on disc nodes)
memory_msg_index_bytesMessage index ETS + processes
memory_other_ets_bytesOther in-memory tables besides those belonging to the stats database and internal database tables
memory_other_proc_bytesMemory used by all other processes that RabbitMQ cannot categorise
memory_other_system_bytesMemory used by all other system that RabbitMQ cannot categorise
memory_plugins_bytesMemory used by plugins (apart from the Erlang client which is counted under Connections, and the management database which is counted separately).
memory_queue_procs_bytesMemory used by class queue masters, queue indices, queue state
memory_queue_slave_procs_bytesMemory used by class queue mirrors, queue indices, queue state
memory_reserved_unallocated_bytesMemory preallocated/reserved by the kernel but not the runtime
memory_total_allocated_bytesNode-local total memory - allocated
memory_total_rss_bytesNode-local total memory - rss
memory_total_erlang_bytesNode-local total memory - erlang

Comparison to official exporter

official exporter.:

  • has runtime/erlang metrics

  • aggregated or per-object metrics

  • missing filter

This exporter:

  • works also with older versions of rabbitmq
  • has more configuration options/ filtering of objects
  • (bad) depends on data from management interface which can be slow/delayed

probalby best solution is to use both exporters: comment from shamil

common errors: Error while retrieving data from rabbitHost / code 500

msg: Error while retrieving data from rabbitHost statusCode: 500

This exporter expects capabilities from rabbitmq 3.6.8 or newer by default. If you are running older than 3.6.8 you have to set RABBIT_CAPABILITIES=compat.

Tag summary

Content type

Image

Digest

sha256:12f27d6d8

Size

7.2 MB

Last updated

over 2 years ago

docker pull kbudde/rabbitmq-exporter:1.0.0