RabbitMQ OpenTelemetry Assets

RabbitMQ is an open-source message broker implementing the Advanced Message Queuing Protocol (AMQP), acting as an intermediary for asynchronous messaging between applications. The RabbitMQ OpenTelemetry assets provide dashboards, alert rules, and SLO templates that visualize and monitor RabbitMQ metrics collected using the OpenTelemetry RabbitMQ receiver, covering queue health, message throughput, consumer availability, and node resource utilization.

The RabbitMQ OpenTelemetry assets have been tested with OpenTelemetry RabbitMQ receiver v0.146.0. The node-level metrics used by the dashboards and alerts require collector-contrib v0.131.0 or later.

RabbitMQ tested against:

• RabbitMQ 3.8, 3.9, 3.10, 3.11, 3.12

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

Enable the RabbitMQ Management plugin so the collector can access the Management API:

rabbitmq-plugins enable rabbitmq_management
		

The Management API listens on port 15672 by default. Create a dedicated monitoring user with appropriate permissions rather than using the default guest account in production. A user with monitoring-level permissions is sufficient.

Install and configure the upstream OpenTelemetry Collector or Elastic Distribution of OpenTelemetry (EDOT) Collector to export metrics to Elasticsearch. Replace the following placeholders in the configuration:

• <ES_API_KEY>: Elasticsearch API key for authentication
• <ES_ENDPOINT>: Elasticsearch endpoint (for example, https://elasticsearch.example.com:9200)
• <RABBITMQ_ENDPOINT>: RabbitMQ Management API endpoint (for example, http://localhost:15672 or http://rabbitmq.example.com:15672)
• <RABBITMQ_USERNAME>: Username for the RabbitMQ Management API
• <RABBITMQ_PASSWORD>: Password for the RabbitMQ Management API. For secrets, use ${env:RABBITMQ_PASSWORD} in the YAML and set the variable in your environment.

receivers:
  rabbitmq:
    endpoint: <RABBITMQ_ENDPOINT>
    username: <RABBITMQ_USERNAME>
    password: <RABBITMQ_PASSWORD>
    collection_interval: 10s
    metrics:
      # Queue-level metrics — required for dashboards, alerts, and SLOs
      rabbitmq.message.current:
        enabled: true
      rabbitmq.message.published:
        enabled: true
      rabbitmq.message.acknowledged:
        enabled: true
      rabbitmq.message.delivered:
        enabled: true
      rabbitmq.message.dropped:
        enabled: true
      rabbitmq.consumer.count:
        enabled: true
      # Node-level metrics disabled by default — required for dashboards and alerts
      rabbitmq.node.mem_used:
        enabled: true
      rabbitmq.node.mem_limit:
        enabled: true
      rabbitmq.node.mem_alarm:
        enabled: true
      rabbitmq.node.disk_free:
        enabled: true
      rabbitmq.node.disk_free_limit:
        enabled: true
      rabbitmq.node.disk_free_alarm:
        enabled: true
      rabbitmq.node.fd_used:
        enabled: true
      rabbitmq.node.fd_total:
        enabled: true
      rabbitmq.node.sockets_used:
        enabled: true
      rabbitmq.node.sockets_total:
        enabled: true
      rabbitmq.node.proc_used:
        enabled: true
      rabbitmq.node.proc_total:
        enabled: true

exporters:
  elasticsearch/otel:
    apm_server_url: <APM_SERVER_URL>
    apm_api_key: <APM_API_KEY>
    sending_queue:
      enabled: true
    mapping:
      mode: otel

service:
  pipelines:
    metrics:
      receivers: [rabbitmq]
      exporters: [elasticsearch/otel]
		

Refer to the metadata.yaml of the OpenTelemetry RabbitMQ receiver for details on available metrics.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.

← →

×

×

×