This alert is related to VerneMQ, a high-performance MQTT broker. It monitors the number of unsuccessful v5 PUBREL
packets sent in the last minute. If you receive this alert, it means that there was an issue with sending PUBREL
packets in your VerneMQ instance.
PUBREL
is a type of MQTT control packet that indicates the release of an application message from the server to the client. It is the third message in the QoS 2 (Quality of Service level 2) protocol exchange, where QoS 2 ensures that a message is delivered exactly once. An unsuccessful v5 PUBREL
packet means that there was an error during the packet processing, and the message wasn't delivered to the client as expected.
VerneMQ logs can give you valuable information about possible errors that might have occurred during the processing of PUBREL
packets. Look for any error messages or traces related to the PUBREL
packets in the logs.
sudo journalctl -u vernemq -f
Alternatively, if you're using a custom log location:
tail -f /path/to/custom/log
Check the logs of the MQTT client that might have caused the unsuccessful PUBREL
packets. Look for any connection issues, error messages, or traces related to the MQTT protocol exchanges.
Verify that the VerneMQ configuration settings related to QoS 2 protocol timeouts and retries are correctly set. Check the VerneMQ documentation for guidance on the proper configuration.
cat /etc/vernemq/vernemq.conf
Use Netdata to monitor VerneMQ metrics to analyze the MQTT server's performance and resource usage. This can help you identify possible issues with the server.
If the above steps don't resolve the alert, look for possible network or service-related issues that might be causing the unsuccessful PUBREL
packets. This could require additional investigation based on your specific infrastructure and environment.