Zabbix trigger configuration
Hi everyone.
I have set up a trigger, this trigger notifies me through Telegram, but the alarms are sometimes recover in milliseconds or sometimes in seconds. The problem is: How can I configure the zabbix trigger to send notifications only when mmm in 5 minutes, for example, I don't have the recovery, but if the alarm is resolved in that time, don't send anything?
I use the Zabbix web app to create the item, and the item reads an ambari-log of a node's state.
I tried using the count() trigger function and an action that waits 3 minutes to send a notification. Then if the alarm is resolved I only have that notification there is no problem notification but in that solution my problem was with the recoveries in milliseconds because I think the zabbix element can't read that fast so it reads the problem but not the resolution, so I have to close manually. And sometimes the resolve log came first in the item. And to give context I have two items because one reads the "CRITICAL" in the log and the recovery item reads the "OK" in the log.
I have set up a trigger, this trigger notifies me through Telegram, but the alarms are sometimes recover in milliseconds or sometimes in seconds. The problem is: How can I configure the zabbix trigger to send notifications only when mmm in 5 minutes, for example, I don't have the recovery, but if the alarm is resolved in that time, don't send anything?
I use the Zabbix web app to create the item, and the item reads an ambari-log of a node's state.
I tried using the count() trigger function and an action that waits 3 minutes to send a notification. Then if the alarm is resolved I only have that notification there is no problem notification but in that solution my problem was with the recoveries in milliseconds because I think the zabbix element can't read that fast so it reads the problem but not the resolution, so I have to close manually. And sometimes the resolve log came first in the item. And to give context I have two items because one reads the "CRITICAL" in the log and the recovery item reads the "OK" in the log.
Comment