Zabbix 4 Network Monitoring - Third Edition

Triggers with a limited period

We discussed hosts and host group maintenance in Chapter 5, Managing Hosts, Users, and Permissions. That allowed us to stop alerting, but when doing so, the smallest entity the maintenance could affect was a host; we could not create a maintenance for a specific trigger without the use of tags. While this is slightly different functionally, we could limit the time for which a trigger is active on the trigger level, too. To do so, we can use several of those time-based trigger functions. Taking our CPU load trigger as an example, we could completely ignore it on Mondays (perhaps there's some heavy reporting done on Mondays):

{A test host:system.cpu.load.avg(180)}>1 and {A test host:system.cpu.load.dayofweek()}<>1 ...