Prometheus and Grafana integration in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Prometheus RabbitMQ Exporter Metrics Output

You run the RabbitMQ Prometheus exporter and query the metric rabbitmq_queue_messages_ready. What output do you expect if the queue task_queue has 5 ready messages?

RabbitMQ

curl http://localhost:9419/metrics | grep rabbitmq_queue_messages_ready

A rabbitmq_queue_messages_ready{queue="task_queue",vhost="/"} 0

B rabbitmq_queue_messages_ready{queue="task_queue"} 0

C rabbitmq_queue_messages_ready{queue="task_queue",vhost="/"} 5

D rabbitmq_queue_messages_ready 5

💡 Hint

Look for the metric with the correct labels showing the queue name and virtual host.

The Prometheus RabbitMQ exporter exposes metrics with labels including queue and vhost. The value shows the number of ready messages. Option C correctly shows 5 ready messages for task_queue in the default virtual host.

❓ Configuration

intermediate

Grafana Data Source Setup for Prometheus

Which configuration snippet correctly sets up a Prometheus data source in Grafana to scrape metrics from http://localhost:9090?

A

apiVersion: 1
datasources:
- name: Prometheus
  type: prometheus
  access: proxy
  url: http://localhost:9090
  isDefault: true

B

apiVersion: 1
datasources:
- name: Prometheus
  type: prometheus
  access: direct
  url: http://localhost:9419
  isDefault: false

C

apiVersion: 1
datasources:
- name: Prometheus
  type: influxdb
  access: proxy
  url: http://localhost:9090
  isDefault: true

D

apiVersion: 1
datasources:
- name: RabbitMQ
  type: prometheus
  access: proxy
  url: http://localhost:9090
  isDefault: true

💡 Hint

Check the data source type and URL for Prometheus.

Grafana data source for Prometheus must have type: prometheus and the correct URL. Option A uses the right URL and sets it as default.

🔀 Workflow

advanced

Order of Steps to Integrate RabbitMQ Metrics into Grafana

What is the correct order of steps to integrate RabbitMQ metrics into Grafana using Prometheus?

A 2,1,3,4

B 1,2,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about enabling metrics first, then scraping, then visualization setup.

First, enable the RabbitMQ exporter to expose metrics. Then configure Prometheus to scrape those metrics. Next, add Prometheus as a data source in Grafana. Finally, create dashboards to visualize the data.

❓ Troubleshoot

advanced

Troubleshooting Missing RabbitMQ Metrics in Grafana

You see no RabbitMQ metrics in Grafana dashboards after setup. Which is the most likely cause?

A Prometheus is not scraping the RabbitMQ metrics endpoint correctly

B Grafana dashboards are missing the Prometheus data source

C RabbitMQ server is down but Prometheus is scraping metrics

D RabbitMQ metrics are visible in Prometheus but Grafana shows no data due to dashboard refresh rate

💡 Hint

Check if Prometheus can access the metrics endpoint first.

If Prometheus cannot scrape the RabbitMQ metrics endpoint, no data will be available for Grafana. Other options either contradict the problem or are less likely.

✅ Best Practice

expert

Best Practice for Securing Prometheus Metrics Endpoint for RabbitMQ

Which option is the best practice to secure the RabbitMQ Prometheus metrics endpoint in a production environment?

A Expose the metrics endpoint publicly without authentication for easy access

B Embed RabbitMQ credentials in Prometheus scrape config without encryption

C Disable TLS and use plain HTTP for metrics to reduce complexity

D Use network policies or firewall rules to restrict access to the metrics endpoint

💡 Hint

Think about limiting who can see sensitive metrics data.

Restricting access to the metrics endpoint using network policies or firewalls is a best practice to protect sensitive data. Public exposure or unencrypted credentials are security risks.

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