My Zabbix server host occasionally reboots (for updates, etc), this results in "Utilization of Zabbix server processes" messages. Since the Zabbix processes are busy just after a restart.
To fix this I'm detect when a reboot occurred, with a nodata trigger on the Zabbix server agent ping.
This trigger is configured as dependency on my "Utilization of Zabbix server processes" triggers. So that they don't send out messages, when the host has been offline/restarted.
This works, however the nodata trigger only lasts for a minute or two. After which data comes in again, and the nodata situation is solved.
Since Zabbix process utilization trigger calculates an average over the last period, and the average utilization is still high, it will still fire the trigger. Is there a way to make the nodata trigger look at an occurrence of nodata in a specific time frame, or to close a trigger after a set time (e.g. 30 minutes).
To fix this I'm detect when a reboot occurred, with a nodata trigger on the Zabbix server agent ping.
This trigger is configured as dependency on my "Utilization of Zabbix server processes" triggers. So that they don't send out messages, when the host has been offline/restarted.
This works, however the nodata trigger only lasts for a minute or two. After which data comes in again, and the nodata situation is solved.
Since Zabbix process utilization trigger calculates an average over the last period, and the average utilization is still high, it will still fire the trigger. Is there a way to make the nodata trigger look at an occurrence of nodata in a specific time frame, or to close a trigger after a set time (e.g. 30 minutes).
Comment