So far, we have only used the two default action conditions. Actually, Zabbix provides quite a lot of different conditions that determine when an action is invoked. Let's look at some examples of what other conditions are available:
- Application: Allows us to limit actions to specific applications. For example, an action could only react when items belonging to the MySQL application are involved. This is a free-form field, so it must match the actual application name. We may also match or negate a sub-string.
- Host: Allows us to single out an important (or unimportant) host for action invocation.
- Host group: Similar to the Host condition, this one allows us to impose a limit based on the host group membership. ...