[ZBXNEXT-1204] Trigger grouping in alerts Created: 2012 Apr 28 Updated: 2018 Jul 03 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Server (S) |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Major |
| Reporter: | Attilla de Groot | Assignee: | Alexei Vladishev |
| Resolution: | Unresolved | Votes: | 7 |
| Labels: | alerts, grouping, trigger | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
Hi, If a host has multiple triggers configured that are related to each other there might be cases where you get alerts for all of these triggers, resulting in a large number of alerts. A practical example would be a router with 30+ cpu's. There might be an issue that causes cpu load on one of them and you want to be alerted about that event. However, another issue might cause high cpu load on all of the cpu's and you don't want to receive alerts on all 30. Thus dependencies are impossible in this situation. |
| Comments |
| Comment by Oleksii Zagorskyi [ 2016 Mar 15 ] |
|
|
| Comment by Vitaly Zhuravlev [ 2017 Aug 31 ] |
|
3.4 network templates( |
| Comment by Oleksii Zagorskyi [ 2018 Jul 03 ] |
|
ZBXNEXT-3849 is distantly related. |
| Comment by Marc [ 2018 Jul 03 ] |
|
Isn't event correlation supposed to deal with such situations? |