I found a possible bug in alpha7.
I have a template that I am using to update all of my servers with basic checks. I have created an NTP check(any plans for a builtin NTP check by any chance?) called, "cust_check_ntp." After testing I noted that there were a few false negatives being alerted so I had to expand the trigger to more thorough expression checking both the last value and the previous value.
Original epxression:
({Zonar.Servers:cust_check_ntp[10.30.0.33].last(0)}=0)
New expression:
({Zonar.Servers:cust_check_ntp[10.30.0.33].last(0)}=0)&({Zonar.Servers:cust_check_ntp[10.30.0.33].prev(0)}=0)
When this gets passed to the other hosts through linkage it is showing up as:
({Hostname.Here:cust_check_ntp[10.30.0.33].last(0)}=0)&({Zonar.Servers:cust_check_ntp[10.30.0.33].prev(0)}=0)
Note the unupdated portion at the end.
Could this possibly be that alpha7 is not evaluating the expression past the ampersand? Thanks,
Jesse
I have a template that I am using to update all of my servers with basic checks. I have created an NTP check(any plans for a builtin NTP check by any chance?) called, "cust_check_ntp." After testing I noted that there were a few false negatives being alerted so I had to expand the trigger to more thorough expression checking both the last value and the previous value.
Original epxression:
({Zonar.Servers:cust_check_ntp[10.30.0.33].last(0)}=0)
New expression:
({Zonar.Servers:cust_check_ntp[10.30.0.33].last(0)}=0)&({Zonar.Servers:cust_check_ntp[10.30.0.33].prev(0)}=0)
When this gets passed to the other hosts through linkage it is showing up as:
({Hostname.Here:cust_check_ntp[10.30.0.33].last(0)}=0)&({Zonar.Servers:cust_check_ntp[10.30.0.33].prev(0)}=0)
Note the unupdated portion at the end.
Could this possibly be that alpha7 is not evaluating the expression past the ampersand? Thanks,
Jesse
, I'll gladly host it at contrib.virkpaanettet.dk (there's a download section).
Comment