Zabbix alarms continue to send historical messages frequently and frequently

Zabbix continuously and frequently sends historical alarm messages, and the alarm content is as high as 1.7w in one night, which seriously affects the viewing of alarm information that really has problems.

Reason for this problem:

  • The backlog of alarm messages is accumulating and is always in the retry state.
  • The trigger does exist, but the status of the target monitoring host is normal. As long as the problem triggered by the trigger exists, an alarm will always occur.

solution:

  • If the trigger problem does exist, but the state of the target host is normal, and alarms are still occurring frequently, if this is the case, manually click to close and confirm the problem to solve the problem. If the trigger is configured in the template , then modify the template directly, and finally close the problem manually.
  • If there is a backlog of messages, then go to the database to delete the alarm of the abnormal state or modify the state to solve the problem.
    mysql> delete from zabbix.alerts where status=2;
    or
    mysql> update zabbix.alerts set status = 1 where status = 2;
    
    status=2: sending failed
    status=1: sending successfully
    status=0: sending

Guess you like

Origin blog.csdn.net/weixin_44953658/article/details/123894016