2 Actions

Overview

If you want some operations taking place as a result of events (for example, notifications sent), you need to configure actions.

Actions can be defined in response to events of all supported types:

• Trigger actions - for events when trigger status changes from OK to PROBLEM and back
• Service actions - for events when service status changes from OK to PROBLEM and back
• Discovery actions - for events when network discovery takes place
• Autoregistration actions - for events when new active agents auto-register (or host metadata changes for registered ones)
• Internal actions - for events when items become unsupported or triggers go into an unknown state

The key differences of service actions are:

• User access to service actions depends on access rights to services granted by user's role
• Service actions support different set of conditions

Configuring an action

To configure an action, do the following:

• Go to Alerts → Actions and select the required action type from the submenu (you can switch to another type later, using the title dropdown)
• Click on Create action
• Name the action
• Choose conditions upon which operations are carried out
• Choose the operations to carry out

General action attributes:

All mandatory input fields are marked with a red asterisk.