Table of Contents
3 Recovery operations
Overview
Recovery operations allow you to be notified when problems are resolved.
Both messages and remote commands are supported in recovery operations. Recovery operations do not support escalating - all operations are assigned to a single step.
Use cases
Some use cases for recovery operations are as follows:
- Notify on a recovery all users that were notified on the problem:
- Select Notify all involved as operation type.
- Have multiple operations upon recovery: send a notification and execute a remote command:
- Add operation types for sending a message and executing a command.
- Open a ticket in external helpdesk/ticketing system and close it when the problem is resolved:
- Create an external script that communicates with the helpdesk system
- Create an action having operation that executes this script and thus opens a ticket.
- Have a recovery operation that executes this script with other parameters and closes the ticket.
- Use the {EVENT.ID} macro to reference the original problem.
Configuring a recovery operation
To configure a recovery operation:
- Go to the Recovery 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.
Recovery operation attributes:
All mandatory input fields are marked with a red asterisk.
| Parameter | Description | ||||
|---|---|---|---|---|---|
| Default subject | Default message subject for recovery notifications. The subject may contain macros. | ||||
| Default message | Default message for recovery notifications. The message may contain macros. | ||||
| Operations | Recovery operation details are displayed. To configure a new recovery operation, click on New. |
||||
| Operation details | This block is used to configure the details of a recovery operation. | ||||
| Operation type | Three operation types are available for recovery events: Send message - send recovery message to specified user Remote command - execute a remote command Notify all involved - send recovery message to all users who were notified on the problem event Note that 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 recovery 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 recovery message to. The user must have at least "read" permissions to the host in order to be notified. |
||||
| Send only to | Send recovery 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 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. | ||||