Is there any way to control how many times a trigger can be activated a day?

[saibuster]

I will use the following example as a case for this question:



This trigger is activated if the Host CPU is averaging 80% for a minute, the trigger is connected to an action that sends an email.
My problem is that in case the machine will average more than 80% CPU for an hour, I will probably get countless email notifications...
Which leads to my question, is there any way to control how many time a trigger can get triggered? For example, it got triggered now and will only
be able to get triggered again after 4 hours.

[kloczek]

Why you are calculating your own cpu avg1 if agent provides this metric OOTB over system.cpu.load[,avg1] ?
Really before reinventing the wheel you should at least try to understand what is implemented in templates provided by Zabbix developers.
https://www.zabbix.com/documentation...s/zabbix_agent
Did you read https://www.zabbix.com/documentation...ion#hysteresis ?

[saibuster]

Thanks for your comment.
I've already read the Hysteresis documentary but couldn't find a way to create a time-based recovery condition that is depending
on the problem creation start time. Any idea if it is possible?