Quest nodata & last

[Alex_SYB]

Hi

i had a tigger setup for a icmppingsec item it was polled every 60sec.. via a proxy.

I set the trigger to
nodata(90)... and it would give me false positive ? the email would show the item with a value !!! i think maybe the event got to the server to late or ?

so now I have changed all my nodata because they were all giving me issues. to last (#1) and last (#2)

Do other people have the same issue, how can I track it down ..

Alex

[heaje]

What macro are you using to get the item's value in your notification? If it is {ITEM.LASTVALUE} then your notification is simply putting in the last value it received for that check. In your case, this is 90 seconds before the alert goes off. Your alert most likely went off because the Zabbix server missed doing the check for some reason. Since your interval is every 60 seconds and the trigger looks for no new data within a 90 second window, you're getting false alerts that probably go away within 90 seconds of the alert going off.

[Alex_SYB]

Hmm , not sure i fully understand the {item.lastvalue}

But I create an item, say for example open a tcp port. say every 30 sec. I then set a trigger on that item of nodata(70)... which to me says if I don't have any data in 70sec that the port is having a problem... maybe a bad example cause i should look at the return value .. but gives the jist of what I was doing.

I have been moving all my nodata to last(#1) and checking values .... but then I need something to say i have received valid data recently !