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. While several operations can be added, escalation is not supported - all operations are assigned to a single step and therefore will be performed simultaneously.

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 Operations tab in action configuration.

To configure details of a new recovery operation, click on in the Recovery operations block. To edit an existing operation, click on next to the operation. A pop-up window will open where you can edit the operation step details.

Recovery operation details

Three operation types are available for recovery events:

Send message - send recovery message to specified user.
Notify all involved - send recovery message to all users who were notified on the problem event.
<remote command name> - execute a remote command. Commands are available for execution if previously defined in global scripts with Action operation selected as its scope.

Parameters for each operation type are described below. All mandatory input fields are marked with a red asterisk. When done, click on Add to add operation to the list of Recovery operations.

Note that if the same recipient is defined in several operation types without specified Custom message, duplicate notifications are not sent.

Operation type: send message

Parameter		Description
Send to user groups		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		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 default recovery message to all defined media types or a selected one only.
Custom message		If selected, a 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

Parameter		Description
Custom message		If selected, a 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.

Documentation