[ZBXNEXT-6237] Avoid duplicative notifications Created: 2020 Oct 06 Updated: 2020 Oct 06 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | New Feature Request | Priority: | Medium |
Reporter: | Nikolay P | Assignee: | Andris Zeila |
Resolution: | Unresolved | Votes: | 1 |
Labels: | actions, notifications | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
It would be nice if there was an option to avoid duplicative notifications fired by multiple actions for the same event to the same user. For example, a trigger "Host unreachable" goes to PROBLEM state and causes two different actions to fire:
If some user "A" is part of these two groups, then he/she will be notified twice for this event. Proposed solution is to make Zabbix detect such scenarios and send only one notification. Perhaps it can be achieved by recording all event IDs that the user was already notified about and not sending the duplicative notifications to the same media. A "notify only once" setting could also exist for enabling/disabling this functionality. Without this functionality one has to come up with sophisticated action settings to avoid multiple notifications for the same event. |