-
New Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Centos 5 production
Our Zabbix environment is setup so that all of our servers have multiple templates applied to them, one is generic and one is specific for the application of the server. In one instance, we have an alert rule created to send notifications to a particular group of users, these users do not need to receive alerts from the generic templates, only from the specific application template. We have setup the condition to alert <> generic_template. This results in no notifications going out on any server, because all of the servers have this template; however, the alert is being generated for the application template, and therefore, should send out a notification.
The workflow should be intellegent enough to note which template is generating the alert and to act accordingly; not apply a blanket condition to the host.