Problem with triggers

[olegv]

Hello,
I have installed Zabbix1.1alpha12 on SUSE9.1.
This triggers do NOT work:
{host:icmpping.max(300)}=0 or
{host:icmpping.min(300)}=0 or
{host:icmpping.avg(300)}=0 or
{host:icmpping.sum(300)}=0
Trigger must send email when host was down for 5 minutes. But when host was going down,
status of trigger does not change and stay FALSE.
But {host:icmpping.last(300)}=0 is working fine and send me alerts when host is down or returns to up.
What's wrong?
I can see a real picture in GRAPH of this item (icmpping) for this host when it is down or returns
to up.
Help, please

[James Wells]

Greetings,

Are you showing multiple individual triggers, or is that a complex trigger? If it is complex trigger, then you have the logic set incorrectly, and needlessly complex. If it is individual triggers, each one should work, however, each will alert in slightly different ways;

{host:icmpping.max(300)}=0 will only trigger when a server has failed to respond to pings for the last 5 minutes

{host:icmpping.min(300)}=0 will trigger any time the server fails to respond to a ping.

{host:icmpping.avg(300)}=0 will only trigger when a server has failed to respond to pings for the last 5 minutes. This could also fail if your periodicity is set to a small enough delay and the server is flapping.

{host:icmpping.sum(300)}=0 will only trigger when a server has failed to respond to pings for the last 5 minutes.

[olegv]

Problem with triggers

it is individual triggers. Either of the four does not work.
When a server has failed to respond to ping, any trigger does not change his status and
stay in FALSE. It is seems to me, functions of trigger "min, max, avg, sum" do not work generally.
"last" function works only.

[innomedia]

If it helps any, I've encountered the same problem with the ping trigger; when the server was disconnected, the trigger in question:
{servername:icmpping.max(300)}<1
remained at 'false', which is strange because looking at the latest data for the server shows that the icmpping value's been 0 for over 4 hours.

Would greatly appreciate it if someone has a answer to this little problem. Thanks!

Edit: tried it with the condition icmp.last(0)=0 and it worked, so it's probably something to do with the max function.

[olegv]

Probably, it's bug in alpha12.
Now I've installed alpha10 and problem is disappeared.
There is not such problem in alpha10.