Notifications

How notifications work?

Anturis enables you to send alert and recovery notifications to different people within your organization, so that the right person is notified when an issue occurs. Notifications can be delivered via email, text message, or over a voice call. If one recipient is unable to deal with or respond to the alert, the alert is automatically sent to the all people on the notifications list.

Configuring notifications

Problem and incident severity helps define which person is notified about an event.
To configure notifications, follow the steps below.
  1. Go to the People and Groups page.
  2. Select a person to receive notifications.
  3. Select Edit.
  4. Open the Notifications tab.
There are two different ways to set up notifications.
  1. You can make a person responsible for more than one component. This person will receive notifications about all problems with the component(s) they are responsible for.
  2. If you want a person to be notified only about incidents, check Notify about all incidents.
Where to set: Go to People and Groups, select the person select Edit and click the General tab.
If the Notify about all incidents is checked, notifications work differently depending on the organization of the infrastructure. The two ways of working with notifications are described below.
  1. When a problem starts in an infrastructure with linked components, one notification is sent – even if several components fail simultaneously. For example, “Incident ... involving … -STARTED”. Additional email-only notifications are sent if a new problem occurs on a higher infrastructure level. Such notifications look like this: “Incident ... involving … -New problem with COMPONENT_NAME”.
  2. When an infrastructure with unlinked components fails, the notification about each failed component is sent to recipients. If several components fail simultaneously, an individual notification is sent for each failed component.
There are four combinations for the settings described above:
  1. Both options are enabled (a person is made responsible for one or several components, and Notify about all incidents is checked for the person).
  2. The responsible person is assigned and Notify about all incidents is not checked.
  3. The responsible person is not assigned and Notify about all incidents is checked.
  4. None of the two options are enabled (no persons are assigned and Notify about all incidents is unchecked).
Outcomes for each of the four combinations:
  1. The person will receive notifications for every problem on the component(s) they are responsible for. Additionally, they will receive notifications about all incidents. In the case of unlinked components, the total number of notifications is doubled and half of them are redundant.
  2. The person will receive notifications for every problem on the component(s) they are responsible for.
  3. The person will receive notifications about all incidents, the number of notifications depends on whether the components are linked or not.
  4. No notifications are sent.
Thus, to optimize notifications flow and receive only important alerts, follow the steps below:
  • Make logical component dependencies.
  • Select the person who needs to be notified about incidents.
  • Select the Notify about all incidents checkbox.
  • DO NOT assign any personal responsibility for individual components.
It is possible to further fine-tune notifications about problem and incident severity, and how a person is notified.