Hi,
I'm currently facing an issue using the nodata() key for a specific item in an SNMP environment using the zabbix_sender.
We're using a redundant environment which consists of several VMWare instances. When shifting from one VM to another VM the trigger which contains the nodata key is TRUE immediately even when the time between shifting is below the nodata(XX) value.
Is there a way to delay the alarming of this specific trigger? I do not have any other issues with triggers within the same template.
Thanks!
I'm currently facing an issue using the nodata() key for a specific item in an SNMP environment using the zabbix_sender.
We're using a redundant environment which consists of several VMWare instances. When shifting from one VM to another VM the trigger which contains the nodata key is TRUE immediately even when the time between shifting is below the nodata(XX) value.
Is there a way to delay the alarming of this specific trigger? I do not have any other issues with triggers within the same template.
Thanks!