Table of Contents
4 Update operations
Overview
Update operations allow you to be notified when problems are updated by other users, i.e.:
- commented upon
- acknowledged
- severity changed
- closed (manually)
Update operations are available in actions with the event source as Triggers.
Both messages and remote commands are supported in update operations. While several operations can be added, escalation is not supported - all operations are assigned to a single step and therefore will be performed simultaneously.
Configuring an update operation
To configure an update operation go to the Operations tab in action configuration.
To configure details of a new update operation, click on 
in the Update operations block. To edit an existing operation, click on 
next to the operation. A popup window will open where you can edit the operation step details.
Update operation details
| Operation | Three operation types are available for update operations: Send message - send update message to specified user when event is updated, for example, acknowledged Notify all involved - send notification message to all users who received notification about the problem appearing and/or have updated the problem event. <remote command name> - execute a remote command when the event is updated, for example, acknowledged. Commands are available for execution if previously defined in global scripts with Action operation selected as its scope. If the same recipient with unchanged default subject/message is defined in several operation types, duplicate notifications are not sent. The person who updates a problem does not receive notification about their own update. |
|||
| Operation type: send message | ||||
| Send to user groups | Click on Add to select user groups to send the update 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 update message to. The user must have at least "read" permissions to the host in order to be notified. |
|||
| Send only to | Send update message to all defined media types or a selected one only. | |||
| Custom message | If selected, the custom message can be defined. | |||
| 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. Specifying a parent host group implicitly selects all nested host groups. Thus the remote command will also be executed on hosts from nested groups. 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. |
|||
| Operation type: notify all involved | ||||
| Default media type | Users who update a problem but have not received notifications about the problem appearing will receive notifications about further updates on the selected default media type - Email or SMS. This field is available since Zabbix 3.4.2. |
|||
| Custom message | If selected, the custom message can be defined. | |||
| Subject | Subject of the custom message. The subject may contain macros. | |||
| Message | The custom message. The message may contain macros. | |||
All mandatory input fields are marked with a red asterisk. When done, click on Add to add operation to the list of Update operations.