Is this a bug or something I am missing?

[aelix]

I have a trigger setup to watch ping times. Every once in a while, the ping will return a single large value, for example 1000ms, which would create a false alert. So in the trigger I decided to make it check for high ping times, but ignore insanely high ping times:

{Standalone_t:icmppingsec.avg(300)}>120&{Standalon e_t:icmppingsec.last(0)}<500

But for some reason, it still triggers for values > 500!?

I also tried this syntax:

({Standalone_t:icmppingsec.avg(300)}>120)&({Standa lone_t:icmppingsec.last(300)}<500)

And it still triggers for high values. Is this a bug or am I mis-interpreting something in the documentation?

[dagof]

In the first case, a sequence of 299 values of 1000 and one of 0 will throw up the trigger, because the average of last 300 is greater than 120 and the last is lower than 500 which is the condition.

Second one same case but with first value with 0 and next 299 with 1000.

I think the condition should be:
({Standalone_t:icmppingsec.avg(300)}>120)&({Standa lone_t:icmppingsec.max(300)}<500)