[ZBXNEXT-1625] Trigger groups for use in actions Created: 2013 Feb 14 Updated: 2013 Feb 14 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | Bas Roos | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | grouping, triggers | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
We are using Zabbix in an environment where multiple departments monitor certain aspects on a list of hosts. Certain triggers/actions only need to be received by one or two department, and some by all. We have partly solved this by putting hosts in certain groups, but there are still single hosts with for instance triggers that will need to go to the systems engineer, and triggers that only need to be sent to the application engineer. |
| Comments |
| Comment by richlv [ 2013 Feb 14 ] |
|
couldn't you use zabbix applications for that ? |
| Comment by Bas Roos [ 2013 Feb 14 ] |
|
Aren't those for items instead of triggers? We have some items that are being used in different triggers, which are for different teams. |
| Comment by richlv [ 2013 Feb 14 ] |
|
ouch. that's not such a common need then |
| Comment by Bas Roos [ 2013 Feb 14 ] |
|
I've used Nagios before for monitoring, which has such a feature, so that's why I was looking for a way to solve it in Zabbix |
