Prometheus and Grafana integration in RabbitMQ - Mini Project: Build & Apply

Prometheus and Grafana Integration with RabbitMQ Metrics

📖 Scenario: You are managing a RabbitMQ server that handles messages for your application. To keep track of its health and performance, you want to collect metrics and visualize them.Prometheus is a tool that collects metrics, and Grafana helps you create dashboards to see those metrics clearly.

🎯 Goal: Set up RabbitMQ metrics collection with Prometheus and create a simple Grafana dashboard to visualize the message rates.

📋 What You'll Learn

Enable the RabbitMQ Prometheus plugin

Configure RabbitMQ to expose metrics on port 15692

Set up Prometheus to scrape RabbitMQ metrics

Create a Grafana dashboard to display message rates

💡 Why This Matters

🌍 Real World

Monitoring RabbitMQ helps ensure your messaging system is healthy and responsive, preventing delays or failures in your application.

💼 Career

DevOps engineers often set up monitoring and alerting for message brokers like RabbitMQ to maintain system reliability.

1

Enable RabbitMQ Prometheus Plugin

Run the command rabbitmq-plugins enable rabbitmq_prometheus to enable the Prometheus plugin in RabbitMQ.

RabbitMQ

# Run the command to enable the Prometheus plugin
# Your code here

Hint

This command activates the plugin that allows RabbitMQ to expose metrics for Prometheus.

2

Configure RabbitMQ Metrics Port

Add the line listeners.tcp.prometheus = 15692 to the RabbitMQ configuration file /etc/rabbitmq/rabbitmq.conf to expose metrics on port 15692.

RabbitMQ

rabbitmq-plugins enable rabbitmq_prometheus
# Add the Prometheus listener port configuration below
# Your code here

Hint

This setting tells RabbitMQ to open port 15692 for Prometheus to collect metrics.

3

Configure Prometheus to Scrape RabbitMQ Metrics

Add this job to the Prometheus configuration file prometheus.yml under scrape_configs: - job_name: 'rabbitmq', static_configs:, - targets: ['localhost:15692'].

RabbitMQ

rabbitmq-plugins enable rabbitmq_prometheus
listeners.tcp.prometheus = 15692
# Add Prometheus scrape job configuration below
# Your code here

Hint

This configuration tells Prometheus where to find RabbitMQ metrics.

4

Create Grafana Dashboard Panel for Message Rates

In Grafana, create a new dashboard and add a panel with the Prometheus query rate(rabbitmq_queue_messages_published_total[5m]) to show the message publish rate over the last 5 minutes.

RabbitMQ

rabbitmq-plugins enable rabbitmq_prometheus
listeners.tcp.prometheus = 15692
scrape_configs:
  - job_name: 'rabbitmq'
    static_configs:
      - targets: ['localhost:15692']
# Add Grafana panel with query below
# Your code here

Hint

This query calculates how many messages are published per second over the last 5 minutes.

Practice

1. What is the first step to enable monitoring of RabbitMQ metrics using Prometheus?

easy

A. Configure Prometheus scrape interval

B. Enable the RabbitMQ Prometheus plugin

C. Install Grafana dashboard

D. Restart the RabbitMQ server

Solution

1. Step 1: Enable RabbitMQ Prometheus plugin

   This plugin exposes RabbitMQ metrics in a format Prometheus can scrape.

2. Step 2: Confirm plugin activation

   Use rabbitmq-plugins enable rabbitmq_prometheus to activate it.

3. Final Answer:

   Enable the RabbitMQ Prometheus plugin -> Option B

4. Quick Check:

   Enable plugin = C [OK]

Hint: Start by enabling the Prometheus plugin in RabbitMQ [OK]

Common Mistakes:

• Trying to configure Prometheus before enabling the plugin
• Assuming Grafana setup is the first step
• Restarting RabbitMQ without enabling the plugin

2. Which of the following is the correct Prometheus scrape configuration snippet to monitor RabbitMQ metrics?

easy

A. scrape_configs:
- job_name: 'rabbitmq'
static_configs:
- targets: ['localhost:15692']

B. scrape_configs:
- job_name: 'rabbitmq'
static_configs:
- targets: ['localhost:5672']

C. scrape_configs:
- job_name: 'rabbitmq'
static_configs:
- targets: ['localhost:15672']

D. scrape_configs:
- job_name: 'rabbitmq'
static_configs:
- targets: ['localhost:9090']

Solution

1. Step 1: Identify RabbitMQ Prometheus metrics port

   The Prometheus plugin exposes metrics on port 15692 by default.

2. Step 2: Verify scrape target in Prometheus config

   The target must be localhost:15692 to scrape RabbitMQ metrics correctly.

3. Final Answer:

   scrape_configs with target localhost:15692 -> Option A

4. Quick Check:

   Port 15692 for Prometheus metrics = A [OK]

Hint: Use port 15692 for RabbitMQ Prometheus metrics scrape [OK]

Common Mistakes:

• Using RabbitMQ AMQP port 5672 instead of metrics port
• Using RabbitMQ management port 15672 incorrectly
• Using Prometheus default port 9090 as target

3. Given this Prometheus scrape config snippet, what will be the result when Prometheus scrapes RabbitMQ metrics?

scrape_configs:
  - job_name: 'rabbitmq'
    static_configs:
      - targets: ['rabbitmq-server:15692']

medium

A. Prometheus will fail due to wrong port

B. Prometheus will ignore this job

C. Prometheus will collect metrics but with errors

D. Prometheus will collect RabbitMQ metrics successfully

Solution

1. Step 1: Check target hostname and port

   The target rabbitmq-server:15692 is valid if DNS resolves and port 15692 is open.

2. Step 2: Confirm Prometheus plugin exposes metrics on port 15692

   This matches the default port for RabbitMQ Prometheus plugin metrics.

3. Final Answer:

   Prometheus will collect RabbitMQ metrics successfully -> Option D

4. Quick Check:

   Correct hostname and port = B [OK]

Hint: Correct hostname and port means successful scrape [OK]

Common Mistakes:

• Assuming port 15692 is incorrect
• Ignoring hostname resolution issues
• Confusing management port with metrics port

4. You configured Prometheus to scrape RabbitMQ metrics but see no data in Grafana dashboards. What is the most likely cause?

medium

A. Prometheus scrape interval is too long

B. Grafana is not installed

C. RabbitMQ Prometheus plugin is not enabled

D. RabbitMQ server is down

Solution

1. Step 1: Check if RabbitMQ Prometheus plugin is enabled

   If the plugin is disabled, no metrics are exposed for Prometheus to scrape.

2. Step 2: Confirm plugin activation with rabbitmq-plugins list

   This command shows enabled plugins; absence of rabbitmq_prometheus means no metrics.

3. Final Answer:

   RabbitMQ Prometheus plugin is not enabled -> Option C

4. Quick Check:

   Plugin disabled = no metrics = A [OK]

Hint: Check plugin enabled before blaming Grafana or Prometheus [OK]

Common Mistakes:

• Assuming Grafana installation causes no data
• Blaming scrape interval without checking metrics exposure
• Ignoring RabbitMQ server status

5. You want to create a Grafana dashboard to monitor RabbitMQ queue length over time. Which data source and query setup is correct?

hard

A. Use Prometheus data source; query rabbitmq_queue_messages_ready

B. Use RabbitMQ data source; query queue_length

C. Use Prometheus data source; query rabbitmq_queue_consumers

D. Use Grafana Loki data source; query queue_length_logs

Solution

1. Step 1: Identify correct data source for RabbitMQ metrics

   Prometheus is used to collect and store RabbitMQ metrics exposed by the plugin.

2. Step 2: Select the metric for queue length

   rabbitmq_queue_messages_ready represents the number of messages ready in queues.

3. Final Answer:

   Use Prometheus data source; query rabbitmq_queue_messages_ready -> Option A

4. Quick Check:

   Prometheus + rabbitmq_queue_messages_ready = D [OK]

Hint: Use Prometheus and metric rabbitmq_queue_messages_ready for queue length [OK]

Common Mistakes:

• Using RabbitMQ data source which is not standard for Grafana
• Querying consumers count instead of queue length
• Using Loki which is for logs, not metrics