Alerting on queue depth and consumer lag in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is queue depth in RabbitMQ?

Queue depth is the number of messages waiting in a queue to be processed by consumers.

beginner

What does consumer lag mean in RabbitMQ?

Consumer lag is the delay or backlog between messages arriving in the queue and being consumed by the consumers.

intermediate

Why is alerting on queue depth important?

Alerting on queue depth helps detect when messages pile up, indicating slow processing or system issues that need attention.

intermediate

Name a common tool used to monitor RabbitMQ metrics like queue depth and consumer lag.

Prometheus is commonly used to collect RabbitMQ metrics, often combined with Grafana for visualization and alerting.

advanced

What RabbitMQ metric can indicate consumer lag?

The 'messages_ready' and 'messages_unacknowledged' metrics together help indicate consumer lag by showing messages waiting and those being processed but not acknowledged.

What does a high queue depth usually indicate in RabbitMQ?

A RabbitMQ server is down

B Messages are piling up and consumers may be slow

C The queue is empty

D Consumers are processing messages faster than they arrive

High queue depth means messages are waiting in the queue, often because consumers are slow or stuck.

Which metric shows messages that are delivered but not yet acknowledged by consumers?

A messages_unacknowledged

B messages_ready

C queue_depth

D consumer_count

messages_unacknowledged counts messages sent to consumers but not yet confirmed as processed.

Which tool is commonly used to visualize RabbitMQ metrics and set alerts?

A Docker

B Jenkins

C GitHub

D Grafana

Grafana is widely used to create dashboards and alerts from metrics collected by Prometheus.

What action should you take if consumer lag is detected?

A Delete the queue

B Ignore it, lag is normal

C Investigate consumer performance and increase capacity if needed

D Restart RabbitMQ server immediately

Consumer lag means consumers are slow; improving consumer speed or adding more consumers helps.

What does 'messages_ready' metric represent?

A Messages waiting in the queue to be delivered to consumers

B Messages already processed

C Number of consumers connected

D Total messages ever sent

messages_ready shows how many messages are waiting in the queue for consumers.

Explain why monitoring queue depth and consumer lag is important in RabbitMQ.

Think about what happens if messages pile up or consumers are slow.

Describe how you would set up an alert for high queue depth in RabbitMQ using monitoring tools.

Consider the flow from metric collection to alert notification.

Practice

1. What is the main reason to set up alerts on RabbitMQ queue depth?

easy

A. To increase the number of queues automatically

B. To delete messages faster from the queue

C. To catch message buildup early and prevent overload

D. To reduce the number of consumers

Solution

1. Step 1: Understand queue depth meaning

   Queue depth is the number of messages waiting in the queue.

2. Step 2: Identify alert purpose

   Alerting on queue depth helps detect when messages pile up, which can cause delays or failures.

3. Final Answer:

   To catch message buildup early and prevent overload -> Option C

4. Quick Check:

   Queue depth alert = catch buildup early [OK]

Hint: Queue depth alert means watching message pileup [OK]

Common Mistakes:

• Thinking alerts delete messages automatically
• Confusing queue depth with consumer count
• Assuming alerts increase queue size

2. Which RabbitMQ command correctly shows the current depth of a queue named task_queue?

easy

A. rabbitmqctl queue_status task_queue

B. rabbitmqctl show_queue task_queue depth

C. rabbitmqctl list_queues name messages

D. rabbitmqctl list_queues name messages_ready messages_unacknowledged

Solution

1. Step 1: Recall correct command syntax

   The command rabbitmqctl list_queues lists queues with specified columns.

2. Step 2: Identify columns showing queue depth

   Columns messages_ready and messages_unacknowledged together show total queue depth.

3. Final Answer:

   rabbitmqctl list_queues name messages_ready messages_unacknowledged -> Option D

4. Quick Check:

   List queues with messages_ready and unacknowledged = A [OK]

Hint: Use list_queues with messages_ready and messages_unacknowledged [OK]

Common Mistakes:

• Using non-existent commands like show_queue
• Omitting messages_unacknowledged count
• Confusing queue_status with list_queues

3. Given this output from rabbitmqctl list_queues name messages_ready messages_unacknowledged:

task_queue  50  10
logs_queue  0   0

What does this indicate about task_queue?

medium

A. There are 60 messages waiting or unacknowledged, indicating possible backlog

B. The queue is empty and consumers are caught up

C. There are 50 consumers connected to the queue

D. The queue is paused and not processing messages

Solution

1. Step 1: Add messages_ready and messages_unacknowledged

   50 + 10 = 60 total messages in or waiting acknowledgment.

2. Step 2: Interpret the meaning

   High number means messages are waiting or not yet processed, showing backlog.

3. Final Answer:

   There are 60 messages waiting or unacknowledged, indicating possible backlog -> Option A

4. Quick Check:

   messages_ready + messages_unacknowledged = backlog [OK]

Hint: Sum ready and unacknowledged messages for total queue depth [OK]

Common Mistakes:

• Confusing messages with consumer count
• Ignoring unacknowledged messages
• Assuming zero means backlog

4. You set an alert on consumer lag but it never triggers even when messages pile up. What is a likely cause?

medium

A. Consumers are processing messages but acknowledgments are delayed

B. The alert threshold is set too high to detect lag

C. The alert monitors only queue depth, not consumer lag

D. RabbitMQ does not support consumer lag monitoring

Solution

1. Step 1: Understand alert configuration

   If alert threshold is too high, small or moderate lag won't trigger alerts.

2. Step 2: Check alert settings

   Adjust threshold to a lower value to catch lag early.

3. Final Answer:

   The alert threshold is set too high to detect lag -> Option B

4. Quick Check:

   High threshold = no alert trigger [OK]

Hint: Check alert thresholds if alerts never trigger [OK]

Common Mistakes:

• Assuming RabbitMQ lacks lag monitoring
• Confusing queue depth with consumer lag
• Ignoring alert threshold settings

5. You want to create an alert that triggers when the task_queue has more than 100 messages waiting or unacknowledged, and consumer lag exceeds 30 seconds. Which approach is best?

hard

A. Use a monitoring tool to query messages_ready, messages_unacknowledged, and consumer lag metrics, then alert if thresholds exceeded

B. Set RabbitMQ to automatically delete messages after 30 seconds

C. Increase the number of consumers without monitoring queue depth

D. Manually check queue depth every hour and restart consumers if needed

Solution

1. Step 1: Identify metrics to monitor

   Queue depth is sum of messages_ready and messages_unacknowledged; consumer lag is time messages wait before processing.

2. Step 2: Use monitoring tool with alert rules

   Set alerts to trigger when queue depth > 100 and lag > 30 seconds for proactive response.

3. Final Answer:

   Use a monitoring tool to query messages_ready, messages_unacknowledged, and consumer lag metrics, then alert if thresholds exceeded -> Option A

4. Quick Check:

   Monitor metrics + alert on thresholds = C [OK]

Hint: Combine queue depth and lag metrics in monitoring alerts [OK]

Common Mistakes:

• Relying on manual checks instead of automated alerts
• Deleting messages automatically without monitoring
• Ignoring consumer lag in alerting