Ad Widget

Collapse

Prevent problem triggering after server short unavailability

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • SimpleRezo
    Junior Member
    • Sep 2020
    • 19

    #1

    Prevent problem triggering after server short unavailability

    Hi

    I have a trigger that checks a timestamp send by agent : the timestamp is the timestamp of a file generated by a script - normally - every minute. I need to be notified if file has not been generated during the last 5 minutes.

    So my expression is :
    Code:
    {<ITEM>.now()}-{<ITEM>.last()}>300
    It's working. But, everytime we stop/start zabbix server for 5 minutes, the problem is raised (probably because the server has not yet received the last value).

    I tried to add
    Code:
    and {<ITEM>.nodata(5m)}=0
    to the trigger but this does not work and after reading https://www.zabbix.com/documentation...gers/functions I think that's because this function might be not usable after server restart (but at least it will prevent firing in case of proxy unavailabity) ?
    Note that this function will display an error if, within the period of the 1st parameter:
    - there's no data and Zabbix server was restarted
    So how I can avoid this "false-positive" after zabbix server stop/start ?
Working...