src/health/guides/vernemq/vernemq_queue_message_drop.md
This alert monitors the number of dropped messages in VerneMQ due to full message queues within the last minute. If you receive this alert, it means that message queues are full and VerneMQ is dropping messages. This can be a result of slow consumers, slow VerneMQ performance, or fast publishers.
Check the message queue length and performance metrics of VerneMQ
Monitor the current message queue length for each topic by using the command:
vmq-admin metrics show | grep queue | sort | uniq -c
You can also monitor VerneMQ performance metrics like CPU utilization, memory usage, and network I/O by using the top command:
top
Identify slow consumers, slow VerneMQ, or fast publishers
Analyze the message flow and performance data to determine if the issue is caused by slow consumers, slow VerneMQ performance, or fast publishers.
Increase the queue length or adjust max_online_messages
If increasing the capacity of your infrastructure is not a viable solution, consider increasing the queue length or adjusting the max_online_messages value in VerneMQ. This can help mitigate the issue of dropped messages due to full queues.
Update the VerneMQ configuration file (vernemq.conf) to set the desired max_online_messages value:
max_online_messages=<your_desired_value>
Then, restart VerneMQ to apply the changes:
sudo service vernemq restart
Monitor the situation
Continue to monitor the message queue length and VerneMQ performance metrics after making changes, to ensure that the issue is resolved or mitigated.