Duplicate email alerts

[cvee.it]

Currently I have configured a custom action which based on a specific trigger will alert a custom message with custom body containing variables of my choosing.


The conditions of the action are (A) & (B).
(A) Trigger value = problem
(B) Trigger ="Template_Name:trigger"

The above works fine. However...

In order to get this to email alert we have a generic admin public folder email account, and therefore all of our alerts are emailed to this public folder, lets call it [email protected]

The action alerting config is set to send message, to single user, admin, email only.

The Admin user has NIWAHD , warning onwards set to active for the email media.

Now because of a combination of how the user is setup with the media to receive WAHD and the custom configuration action, I get duplicate emails :

1 . with the generic trigger = problem
2. the custom configuration action described above.


What I've tried so far:
I tried changing the trigger rank to something other than what the user auto-email alerts for, so the NI (Not classified & Information), of NIWAHD , but that just didnt email at all as it wasnt something the admin user was eligible for due to the media configuration of that user.

Therefore now I get duplciate emails, one simple, one custom, and its getting really spammy. I'm temped to just drop these at our mail server, but I'd like to think I can work around the problem within Zabbix and how I have it configured.

Thoughts?

[unnisathya]

Same Issue Here!!!

Hi,


I have got all the default setting and had created a chain of item, trigger, action but now for each trigger I recieve 6 mails. I dont know what the count of 6 identical mails mean one after the other comes, making it really spammy in my inbox.


Guys any Idea??

[cvee.it]

When in doubt, throw it out

Without any sort of community suggestions I ended up dropping the duplicate emails at our mail server ( exchange).

Basically the trigger in question " trigger name = trigger value" but then to make is slightly different in the configurable action, I added a prefix. So my exchange drop rule filter would exclude the emails with the prefix I added specific to the action.

Now I just get a single action email, with trigger.value = problem with no 'okay' values or anything, and for now its suiting my purposes, but its just a hack job really.

[tom.blackstone]

I had this problem as well, and found it was a "generic" trigger action I had created, which I was using as a template to clone as I created individual Actions for my different servers. When I created the Action, I did trigger severity equals Disaster or High (A or B) but no C (such as a server name) so it was acting on anything. I discovered this when I disabled all the Trigger Actions I created for my servers and I still received email notifications.