The scenario is as follows:
Zabbix 7.4.5 is monitoring a log file on an Ubuntu server, where several remote clients write a status message every 60 seconds.
The status messages are something like: "STATION xxx - OK", or "STATION xxx - OFFLINE".
So the log monitoring item is like this:
I'm trying to create a trigger that fires if a station is OFFLINE for 3 (or more) consecutive minutes. So the trigger is like this:
What's wrong with this?
Previously I used another trigger that fires immediately at the first "OFFLINE" occurrence, using 'find' instead of 'count', which worked perfectly. Now I want the trigger to fire if the station X stays offline for 3 or more minutes, but the trigger I designed does not seem to work.
Zabbix 7.4.5 is monitoring a log file on an Ubuntu server, where several remote clients write a status message every 60 seconds.
The status messages are something like: "STATION xxx - OK", or "STATION xxx - OFFLINE".
So the log monitoring item is like this:
I'm trying to create a trigger that fires if a station is OFFLINE for 3 (or more) consecutive minutes. So the trigger is like this:
What's wrong with this?
Previously I used another trigger that fires immediately at the first "OFFLINE" occurrence, using 'find' instead of 'count', which worked perfectly. Now I want the trigger to fire if the station X stays offline for 3 or more minutes, but the trigger I designed does not seem to work.
(it is an additional condition, that has to be true AFTER original expression has been calculated to false)...
Which still can happen, but if you have 150 endpoints writing there once a minute... you probably get more than 3 per check ... and not 3 times from same endpoint...
Comment