Key metrics to monitor in RabbitMQ - Commands & Configuration

Introduction

Monitoring key metrics in RabbitMQ helps you keep your message broker healthy and efficient. It shows you if messages are flowing well or if there are problems like slow consumers or full queues.

When you want to check if your RabbitMQ server is handling messages without delays

When you need to find out if queues are filling up and might cause message loss

When you want to monitor how many messages are being published and consumed

When you suspect consumers are slow or stuck and want to confirm

When you want to track resource usage like memory and disk to avoid crashes

Commands

This command shows the overall status of the RabbitMQ server including memory, disk, and running nodes.

Terminal

rabbitmqctl status

Expected Output

Status of node rabbit@my-server ...

[{pid,12345},

 {running_applications,[{rabbit,"RabbitMQ","3.11.10"},{os_mon,"CPO  CXC 138 46"}]},

 {memory,[{total,104857600},{connection_readers,123456},{connection_writers,123456}]},

 {disk_free,5000000000},

 {alarms,[]}]

Lists all queues with their name, number of messages ready to be delivered, and number of consumers connected.

Terminal

rabbitmqctl list_queues name messages consumers

Expected Output

queue1	10	2

queue2	0	1

queue3	5	0

Shows all exchanges with their type and the number of messages published to them.

Terminal

rabbitmqctl list_exchanges name type messages

Expected Output

amq.direct	direct	100

amq.fanout	fanout	50

my-exchange	direct	200

Displays all current connections with their state and how many channels each connection has open.

Terminal

rabbitmqctl list_connections name state channels

Expected Output

127.0.0.1:5672	running	3

192.168.1.10:5672	running	1

Lists consumers for each queue, showing if they require acknowledgments which affects message reliability.

Terminal

rabbitmqctl list_consumers queue consumer_tag ack_required

Expected Output

queue1	consumer1	true

queue2	consumer2	false

Key Concept

If you remember nothing else from monitoring RabbitMQ, remember: watch queue message counts and consumer activity to catch bottlenecks early.

Common Mistakes

Ignoring the number of consumers on a queue

If no consumers are connected, messages pile up and cause delays or memory issues.

Always check consumers count with queues to ensure messages are being processed.

Not monitoring memory and disk usage

RabbitMQ can crash or slow down if memory or disk space runs out.

Use 'rabbitmqctl status' regularly to watch resource usage.

Only checking messages published but not messages ready in queues

High published messages with low ready messages might hide consumer problems.

Check both published messages on exchanges and ready messages in queues.

Summary

Use 'rabbitmqctl status' to check server health and resource usage.

List queues with message and consumer counts to find bottlenecks.

Check exchanges for message publishing rates.

Monitor connections and consumers to ensure smooth message flow.

Practice

1. Which key metric helps you understand how many messages are waiting to be processed in RabbitMQ?

easy

A. Number of open connections

B. Queue length (number of messages ready or unacknowledged)

C. CPU usage of the RabbitMQ server

D. Disk space available on the server

Solution

1. Step 1: Understand message queue metrics

   The queue length shows how many messages are waiting or being processed, indicating workload.

2. Step 2: Identify the metric related to message backlog

   Queue length directly reflects message counts, unlike connections or CPU usage.

3. Final Answer:

   Queue length (number of messages ready or unacknowledged) -> Option B

4. Quick Check:

   Message backlog = Queue length [OK]

Hint: Messages waiting = queue length metric [OK]

Common Mistakes:

• Confusing connections count with message count
• Thinking CPU usage shows message backlog
• Ignoring unacknowledged messages in queue length

2. Which of the following rabbitmqctl commands correctly shows the number of connections to the RabbitMQ server?

easy

A. rabbitmqctl list_connections

B. rabbitmqctl show_connections

C. rabbitmqctl get_connections

D. rabbitmqctl connections_list

Solution

1. Step 1: Recall the correct command syntax

   The official command to list connections is rabbitmqctl list_connections.

2. Step 2: Verify other options are invalid

   Commands like show_connections, get_connections, and connections_list do not exist in rabbitmqctl.

3. Final Answer:

   rabbitmqctl list_connections -> Option A

4. Quick Check:

   List connections command = rabbitmqctl list_connections [OK]

Hint: Use 'list_connections' to see active connections [OK]

Common Mistakes:

• Using incorrect command verbs like show or get
• Mixing up command word order
• Assuming all commands start with 'get_'

3. Given the output of rabbitmqctl list_queues name messages_ready messages_unacknowledged as:

queue1 10 5
queue2 0 0
queue3 3 2

What is the total number of messages currently in all queues?

medium

A. 5

B. 15

C. 20

D. 10

Solution

1. Step 1: Sum messages_ready and messages_unacknowledged per queue

   queue1: 10 + 5 = 15, queue2: 0 + 0 = 0, queue3: 3 + 2 = 5

2. Step 2: Add totals from all queues

   15 + 0 + 5 = 20 total messages in all queues

3. Final Answer:

   20 -> Option C

4. Quick Check:

   Total messages = 20 [OK]

Hint: Add ready + unacknowledged messages for total [OK]

Common Mistakes:

• Counting only ready messages
• Ignoring unacknowledged messages
• Adding queue names instead of numbers

4. You run rabbitmqctl list_queues name messages_ready but get an error: unknown command. What is the most likely cause?

medium

A. The Management Plugin is not enabled

B. RabbitMQ server is not running

C. You do not have permission to run rabbitmqctl

D. The command syntax is incorrect or incomplete

Solution

1. Step 1: Check command syntax

   The command rabbitmqctl list_queues name messages_ready is valid, but if typed incorrectly or missing parts, it causes 'unknown command'.

2. Step 2: Rule out other causes

   Management Plugin absence does not cause this error; server down or permission issues give different errors.

3. Final Answer:

   The command syntax is incorrect or incomplete -> Option D

4. Quick Check:

   Syntax error = unknown command [OK]

Hint: Check command spelling and arguments carefully [OK]

Common Mistakes:

• Assuming plugin missing causes unknown command
• Ignoring typos in command
• Confusing permission errors with syntax errors

5. You want to monitor RabbitMQ queue health by alerting when the total messages (ready + unacknowledged) exceed 1000. Which approach is best to automate this monitoring?

hard

A. Use the Management Plugin's HTTP API to fetch queue metrics and trigger alerts

B. Manually run rabbitmqctl list_queues daily and check counts

C. Check server CPU usage as a proxy for queue length

D. Restart RabbitMQ server every hour to clear queues

Solution

1. Step 1: Identify automated monitoring methods

   The Management Plugin provides an HTTP API to programmatically get queue metrics for automation.

2. Step 2: Evaluate options for alerting

   Manual checks are slow and error-prone; CPU usage does not reflect queue length; restarting server is disruptive and not a solution.

3. Final Answer:

   Use the Management Plugin's HTTP API to fetch queue metrics and trigger alerts -> Option A

4. Quick Check:

   Automate with API = best practice [OK]

Hint: Automate with Management Plugin API for alerts [OK]

Common Mistakes:

• Relying on manual checks
• Using unrelated metrics like CPU usage
• Restarting server to fix queue issues