Table of Contents
4 Acknowledgement operations
Overview
Acknowledgement operations allow you to be notified when problems are acknowledged.
Acknowledgement operations are available in actions with the event source as Triggers.
Both messages and remote commands are supported in acknowledgement operations. Acknowledgement operations do not support escalating - all operations are assigned to a single step.
Configuring an acknowledgement operation
To configure a acknowledgement operation:
- Go to the Acknowledgement operations tab in action configuration
- Click on New in the Operations block
- Edit the operation details and click on Add
Several operations can be added.
Acknowledgement operation attributes:
| Parameter | Description | ||||
|---|---|---|---|---|---|
| Default subject | Default message subject for acknowledgement notifications. The subject may contain macros. | ||||
| Default message | Default message for acknowledgement notifications. The message may contain macros. | ||||
| Operations | Acknowledgement operation details are displayed. To configure a new acknowledgement operation, click on New. |
||||
| Operation details | This block is used to configure the details of an acknowledgement operation. | ||||
| Operation type | Three operation types are available for acknowledgement operations: Send message - send acknowledgement message to specified user when event is acknowledged Remote command - execute a remote command when event is acknowledged Notify all involved - send notification message to all users who received notification about the problem appearing and/or have acknowledged the problem event. The person who acknowledges does not receive notification about their own acknowledgement. (Note that this option was called Notify all who left acknowledgement and comments in Zabbix 3.4.0-3.4.1 and would only send message to those who acknowledged and commented on the problem.) If the same recipient with unchanged default subject/message is defined in several operation types, duplicate notifications are not sent. |
||||
| Operation type: send message | |||||
| Send to user groups | Click on Add to select user groups to send the acknowledgement 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 acknowledgement message to. The user must have at least "read" permissions to the host in order to be notified. |
||||
| Send only to | Send acknowledgement message to all defined media types or a selected one only. | ||||
| Default message | If selected, the default message will be used (see above). | ||||
| 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. |
||||
| 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 agent - the script will be executed by Zabbix agent on the host Zabbix server (proxy) - the script will be executed by Zabbix server or proxy - depending on whether the host is monitored by server or proxy Zabbix server - the script will be executed by Zabbix server only 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). |
||||
| Operation type: notify all involved | |||||
| Default media type | Users who acknowledge a problem but have not received notifications about the problem appearing will receive notifications about further acknowledgements on the selected default media type - Email, Jabber or SMS. This field is available since Zabbix 3.4.2. |
||||
| Default message | If selected, the default message will be used (see above). | ||||
| Subject | Subject of the custom message. The subject may contain macros. | ||||
| Message | The custom message. The message may contain macros. | ||||