Why Prometheus and Grafana integration in RabbitMQ? - Purpose & Use Cases

The Big Idea

What if you could see your RabbitMQ's health at a glance and stop problems before they start?

The Scenario

Imagine you run a busy RabbitMQ server and want to know how many messages are waiting or how fast they are processed.

You try to check this by logging into the server and running commands one by one every few minutes.

This means you have to watch many numbers and guess if something is wrong.

The Problem

This manual checking is slow and tiring.

You might miss important problems because you can't watch everything at once.

Also, it's easy to make mistakes or forget to check at the right time.

The Solution

Prometheus automatically collects all the important RabbitMQ data for you.

Grafana then shows this data in clear, colorful graphs and dashboards.

You can see everything live and spot problems quickly without guessing.

Before vs After

✗ Before

rabbitmqctl list_queues
rabbitmqctl list_connections

✓ After

Prometheus scrapes metrics endpoint
Grafana displays dashboards

What It Enables

You get real-time, easy-to-understand views of your RabbitMQ health and performance, helping you fix issues before they grow.

Real Life Example

A company uses Prometheus and Grafana to watch their RabbitMQ queues during a big sale.

When message delays start, they see it immediately on Grafana and fix the problem fast, avoiding customer complaints.

Key Takeaways

Manual monitoring is slow and error-prone.

Prometheus collects data automatically.

Grafana shows data visually for quick understanding.

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