Hello community
In this template, which is present in the Zabbix server, 2 triggers are stored. "{#UNIT.NAME}: Service is not running" and "{#UNIT.NAME}: has been restarted (uptime < 10m)".
We use this template to monitor our Linux servers. But now we have the following problem:
At night (or even in the morning) updates are automatically applied to the servers. After that the services are restarted under Linux. Since we have quite a few servers in Zabbix, this creates a flood of emails and events.
How can the trigger "{#UNIT.NAME}: Service is not running" be changed so that it generates a warning only after 20 minutes and does nothing before? It is very unpleasant to generate such a mass of messages and emails every day.
I hope you can help me somehow.
In this template, which is present in the Zabbix server, 2 triggers are stored. "{#UNIT.NAME}: Service is not running" and "{#UNIT.NAME}: has been restarted (uptime < 10m)".
We use this template to monitor our Linux servers. But now we have the following problem:
At night (or even in the morning) updates are automatically applied to the servers. After that the services are restarted under Linux. Since we have quite a few servers in Zabbix, this creates a flood of emails and events.
How can the trigger "{#UNIT.NAME}: Service is not running" be changed so that it generates a warning only after 20 minutes and does nothing before? It is very unpleasant to generate such a mass of messages and emails every day.
I hope you can help me somehow.
Comment