Dedupe Event Action Notifications

[tangel]

Is there anyway to avoid sending more than one email to the same email address/media even if triggered by multiple actions? I believe emails are deduped within a single action but not across multiple actions even if spawned by the same event.

For instance, if a user is a member of both the Oracle DBA user group and the Solaris admins group and two separate actions drive the notifications for those two groups, the user will get two identical problem and recovery emails.


Any ideas for working around this would be appreciated!

[xs-]

I've had the same question a while ago.

Keep in mind tho, that different actions also have (possibly) different messages. How would zabbix know which of the two it should pick for sending.

[tangel]

You bring up a good point with the messages.

I've given it some thought and, rather than make it the default behaviour, I think a dedupe alerts checkbox on the actions page would do the trick. Then, before sending an alert, do a query for the event_id and email address.

The issue then becomes which one gets sent if they all fire at the same time. Not sure how to make that work in a consistent and intuitive way.

[xs-]

On the other hand, it seems that you are working in a larger environment using separate tech groups and assignments.
What you could also do, is (partially) lose the action condition on hostgroup and start using either the 'linked template' condition or the application condition. It requires some pre-planning but this way you could route triggers in a more specific way.
I.e. Oracle admins don't care about OS related stuff, SUN admins don't care about Oracle stuff. If you use the hostgroup/host condition, all triggers from a host are send to your defined group(s), if you use conditions based on specific trigger(groups) or items, its more specific and would have a lower chance of duplicate messages in your situation.

[tangel]

Good ideas that require a bit of rework. I'll try to post back what I go with...

Thanks!