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.