In CloudAMQP, consumer alarms can be configured to notify you when a queue gets fewer consumers than a configurable threshold. Keeping track of the number of consumers in a queue is useful in case there are no consumers, which makes the queue too large and impacts performance. On the other hand, it can also help you see that your clients are working and haven't stopped for some reason.
Previously, consumer alarms monitored all queues and sent a notification for each missing consumer. However, this has proven not to be the best scenario, as if one service goes down that consumes from many queues, you will get a lot of emails or alarms depending on the configurations. To avoid this, consumer alarms has been changed to only send notifications when any queue is missing a consumer. If you wish to be notified on a different set of queues, just create more consumer alarms and specify a regex for either the virtual host or a subset of queues that you wish to monitor.
Keep in mind that if one queue triggers the alarm because of missing consumers, you will not get another notification if the same thing happens to another queue. Create two alarms to match the two different queues to get around this.
We hope you will find this update useful. As always, if you have any questions, don’t hesitate to reach out to the support team. And if you haven’t already added consumer alarms, it’s time to do so!
Best of luck,
/Magnus and the CloudAMQP team
