Action oddness

[elkor]

OK, maybe I'm missing something here, as I did a search and I did not see anyone else really complaining about it.

I just did a b1 to b8 upgrade and got everything running. I am now dealing with the syntax changes and new way that actions work.

I like the new actions, it should really allow me to reduce the number of entries there.

BUT

host group doesn't seem to work?

example:

I have 2 actions configured

1st with conditions: host = Ix

2nd with conditions: host group = Mail Gateways, Trigger Severity <> Information

Both actions are enabled

Ix is not a member of Mail Gateways and I has 1 item/trigger defined that chksums inetd.conf with a severity of average.

NOW, when I change inetd.conf I get 4 alerts, 2 on 2 off.
This shouldn't happen because the second action should be ignored (Ix is not a member of Mail Gateways) but it isn't. This led me to believe that the conditions list was performing a logical OR instead of an AND, so I added a third condition

trigger value = ON

after adding this and rerunning the test I get 3 mail messages, an on and an off from alert 1, and a single on from alert 2.

This just doesn't make sense! if the conditions were an OR then I would still get 4 alerts (because of the trigger severity condition), I don't understand how the action conditions effect the executions of actions (unless it's a bug)

can anybody shed a little light on this scenario or run a test themselves? please? ;)

[elkor]

OK,

I think I may have figured out what is wrong here. And I believe it's a bug.

Ix was not in ANY of my configured host groups, when I added it to the web servers one, the erroneous alert from trigger 2 ceased. it looks like the above problem will occur if your action is based on host groups and a host who is not a member of any group encounters an issue.

This means that if your actions are configured in this way, and a "lone" host lights up a trigger, you will get an email (or remote action!!!!! :eek: ) for every alert that is configured to fire based on host group membership.

I would still like some independent verification of this if possible, I am running 1.1beta8 on the server side; so if either Alexei or someone else with a testbed could chime in and let me know I'm not crazy it would be appreciated :)

[elkor]

another potential problem:

http://www.zabbix.com/forum/showthread.php?p=8668#post8668

I really really do not want to scrap a beta8 rollout here over this.