You can define the following operations for all events:
For discovery events, there are additional operations available:
The additional operations available for auto-registration events are:
To configure an operation, go to Operations tab in the action properties form and click on New. Edit the operation step and click on Add to add to the list of Action operations.
|Default operation step duration||Duration of one operation step by default (minimum 60 seconds).
For example, an hour-long step duration means that if an operation is carried out, an hour will pass before the next step.
|Action operations||Action operations are displayed, with these details:
Steps - escalation step(s) to which the operation is assigned
Details - type of operation and its recipient/target.
Since Zabbix 2.2, the operation list also displays the media type (e-mail, SMS, Jabber, etc) used in sending a message as well as the name and surname (in parentheses after the alias) of a notification recipient.
Start in - how long after an event the operation is performed
Duration (sec) - step duration is displayed. Default is displayed if the step uses default duration, and a time is displayed if custom duration is used.
Action - links for editing and removing an operation are displayed.
To configure a new operation, click on New.
|Operation details||This block is used to configure the details of an operation.|
|Step||Select the step(s) to assign the operation to in an escalation schedule:
From - execute starting with this step
To - execute until this step (0=infinity, execution will not be limited)
Step duration - custom duration for these steps (0=use default step duration).
Several operations can be assigned to the same step. If these operations have different step duration defined, the shortest one is taken into account and applied to the step.
|Operation type||Two operation types are available for all events:
Send message - send message to user
Remote command - execute a remote command
More operations are available for discovery and auto-registration based events (see above).
|Operation type: send message|
|Send to user groups||Click on Add to select user groups to send the message to.
The user group must have at least “read” permissions to the host in order to be notified.
|Send to users||Click on Add to select users to send the message to.
The user must have at least “read” permissions to the host in order to be notified.
|Send only to||Send message to all defined media types or a selected one only.|
|Default message||If selected, the default message will be used (see general action attributes).|
|Subject||Subject of the custom message. The subject may contain macros.|
|Message||The custom message. The message may contain macros.|
|Operation type: remote command|
|Target list||Select targets to execute the command on:
Current host - command is executed on the host of the trigger that caused the problem event. This option will not work if there are multiple hosts in the trigger.
Host - select host(s) to execute the command on.
Host group - select host group(s) to execute the command on.
A command on a host is executed only once, even if the host matches more than once (e.g. from several host groups; individually and from a host group).
The target list is meaningless if the command is executed on Zabbix server. Selecting more targets in this case only results in the command being executed on the server more times.
Note that for global scripts, the target selection also depends on the Host group setting in global script configuration.
|Type||Select the command type:
IPMI - execute an IPMI command
Custom script - execute a custom set of commands
SSH - execute an SSH command
Telnet - execute a Telnet command
Global script - execute one of the global scripts defined in Administration→Scripts.
|Execute on||Execute a custom script on Zabbix server or Zabbix agent. To execute scripts on the agent, it must be configured to allow remote commands from the server.
This field is available if 'Custom script' is selected as Type.
|Commands||Enter the command(s).
Supported macros will be resolved based on the trigger expression that caused the event. For example, host macros will resolve to the hosts of the trigger expression (and not of the target list).
|Conditions||Condition for performing the operation:
Not ack - only when the event is unacknowledged
Ack - only when the event is acknowledged.