hi
i'm hoping someone can point out where i'm going wrong with the trigger time() function.
i'm using the folllowing expression to monitor a process called MailStats ourtside of the hours of 00:00 & 02:00 (when the process is stopped for backups):
{myhost
roc.num[,,,MailStats].last(0)}=0 & {myhost
roc.num[,,,MailStats].time(0)}>020000 & {myhost
roc.num[,,,MailStats].time(0)}<000000
but the trigger keeps paging. i''ve played around with variations on the above such as:
{myhost
roc.num[,,,MailStats].last(0)}=0 & (({myhost
roc.num[,,,MailStats].time(0)}>020000)|({myhost
roc.num[,,,MailStats].time(0)}<000000))
but same result - the zabbix server seems to ignore the time function. worse, it seems that outside the period defined (00:00 - 02:00) the trigger doesn't trigger anymore.
and of course if i remove the time functions the trigger alerts fine...
i've also tested using a basic icmpping trigger and i get the same results so it's not specific to the proc.num function
is there something i'm missing here to get the time function to work?
i've tested the same expression on zabbix 1.6.5 and 1.4.2 so i'm pretty sure it's something i'm doing (or not doing).
any help much appreciated!
i'm hoping someone can point out where i'm going wrong with the trigger time() function.
i'm using the folllowing expression to monitor a process called MailStats ourtside of the hours of 00:00 & 02:00 (when the process is stopped for backups):
{myhost
roc.num[,,,MailStats].last(0)}=0 & {myhost
roc.num[,,,MailStats].time(0)}>020000 & {myhost
roc.num[,,,MailStats].time(0)}<000000but the trigger keeps paging. i''ve played around with variations on the above such as:
{myhost
roc.num[,,,MailStats].last(0)}=0 & (({myhost
roc.num[,,,MailStats].time(0)}>020000)|({myhost
roc.num[,,,MailStats].time(0)}<000000))but same result - the zabbix server seems to ignore the time function. worse, it seems that outside the period defined (00:00 - 02:00) the trigger doesn't trigger anymore.
and of course if i remove the time functions the trigger alerts fine...
i've also tested using a basic icmpping trigger and i get the same results so it's not specific to the proc.num function
is there something i'm missing here to get the time function to work?
i've tested the same expression on zabbix 1.6.5 and 1.4.2 so i'm pretty sure it's something i'm doing (or not doing).
any help much appreciated!
Comment