Strange trigger behaviour in 1.1beta8

[technow0rker]

Hi there.

I am observing strange trigger behaviour in 1.1beta8.
For passively (i.e. without agent running) monitored hosts I've defined special template named ICMP.ping with items icmpping and icmppingsec and check frequency 60 and 300 sec respectively and linked all targets of that type to the template.

Next, I've defined trigger named "No ICMP ping to {HOSTNAME}" with key value of ({ICMP.ping:icmpping.last(0)})=0. That works OK, but if I try to define trigger with key value of ({ICMP.ping:icmpping.sum(300)})<2 which meant to be "Less than 2 successful icmp pings over 300 sec period", it never fires up.

Is this a misconfiguration/misunderstanding issue or this is a bug?


Sincerely,
Alexander Khimich

[elkor]

I could be wrong here.. I'm only working with templates starting just now.

but wouldn't you need to do

({{HOSTNAME}:icmpping.sum(300)})<2

in order to get this to fire on individual hosts? does a template name automatically expand to hostname for linked hosts on triggers?

[technow0rker]

Well, triggers in Host.Unix (for example) are defined in such way, Host.Unix is substituted then with actual host name, and they work.

Strange.