(DI-1902) Alert Definition

Definition of alerts

There are three options how to define an new alert.

1.  A simple solution is to use the context menu of a KPI and choose to create an alert. Please see more information under the KPI context menu.

2. The second option is to define alerts in the monitoring customizing with the following steps:

Go to Settings > Monitoring settings. Select a KPI from KPI definitions and choose the option Assign alerts. Then, create a new entry for an alert definition or edit an existing one. You can create only an alert with the threshold kind. For each newly created alert you must define at least one threshold value. Please see the figure Threshold setup.

Threshold setup

3. The third option is to define alerts in monitoring customizing by selecting Alerts in the tree view and defining the bellow mentioned fields.

This definition consists of:

• Name and description – a unique, case sensitive technical name of an alert.
  Please note that you can create or modify only field names (in this case the alert name) that start with Z*, Y* (or X* for generated alert names). The standard customizing (field entries except the ones starting with Z*, Y*, X*) can not be changed or added.
• KPI name and description – name of KPI, based on which an alert is created
• Long description – the description of the alert is used as the label in outputs.
• Type – describes the alert type and determines which icon appears, if the alert occurs. Possible values are:
  • Success – 
  • Warning – 
  • Issues – 
  • Error - 
• Kind – defines the kind of an alert (Threshold or Anomaly).
• Period time – the frequency that specifies how often an alert is checked.
• Changelog – displays the user name and time, when the alert was created and changed.

Every alert created is necessary to assign to a KPI and to a Profile. This is performed according to the type of alert in Threshold setup by filling the following fields:

Threshold setup

Select New Entries and fill in the following fields:

• System ID – alert is checked only for this system.
• Profile – alert is checked only for this profile.
• Valid from – time from when the alert is checked. If the field Valid from isn't set, it is filled automatically with the time of the threshold creation.
• Valid to – time until when the alert is checked. If the field Valid to isn't set, the alert is checked infinitely.
• Operator – determines in which case a KPI value causes an alert to occur.
  

      _{Comparison operator}

• Threshold – determines the limit value for a KPI. The alert occurs, if the KPI exceeds its defined threshold.
• Unit – determines the used unit of measurement, for example %, MB, etc.
• Duration start – how long can a KPI value exceed the threshold (in grey area) before an alert occurs.
• Duration end – how long a KPI value has to be outside of the threshold area (in grey area) before an alert is stopped.

_{Threshold setup}

Anomaly view

In the Anomaly view you can only display the existing anomaly alert settings. In this view it isn't possible to create new settings for an anomaly alert. In the case you want to create a new setting or change the existing one, go to the context menu of a KPI in the Monitoring Cockpit.

• System ID – the alert is checked only on this system. In the case that this field is empty, alert is checked on all systems. 
• Profile – alert is checked only for this profile. In the case that this field is empty, alert is checked for all profiles.
• Valid from – time from when the anomaly is checked. If the field Valid from isn't set, it is filled automatically with the time of the anomaly creation.
• Valid to – time until when the anomaly is checked. If the field Valid to isn't set, the alert is checked infinitely.
• Parameter name – defines a name of a setting, which is used in anomaly detection. Each anomaly alert consists of the following settings:
  • Detection type –specifies a method of anomaly detection
  • High percentile – defines a value of high percentile, which is used in the calculation method of the anomaly detection
  • Low percentile  – defines a value of low percentile, which is used in the calculation method of the anomaly detection
  • Moving window – defines how many KPI values from the history should be included in the calculation method of the anomaly detection
  • Percentile type – defines which KPI values are excluded from the calculation method of the anomaly detection
    • L (Low) - only those KPI values are excluded, which values are lower than the value of low percentile
    • H (High) - only those KPI values are excluded, which values are higher than a value of high percentile
    • M (Low + High) - subtraction of high and low percentile values. In this case the interquartile range (IQR) method for anomaly detection is used. 
  • Status – specifies status of anomaly detection
    • A (Active) - anomaly detection is enabled when Collector job is running 
    • W (Waiting) - anomaly detection is enabled when Collector job is running, but there are not enough KPI values collected yet. Number of collected KPI values is less than the size of the moving window. 
    • C (Closed) - anomaly detection is disabled
    • S (Simulation) - this status is created, when you execute the simulation of anomaly detection on the historical KPI values. 
• Parameter value - defines a value, which is used in anomaly detection calculation method 

Anomaly view

Notification 

You may be notified about each alert occurrence by email or by message in SAP Business Workplace. This is performed under Notification of this view. The following fields should be filled:

• System ID - you receive notifications of alerts, which occurred on the entered system ID. In the case that this field is empty, notifications are sent from all systems. 
• Profile –  you receive notifications of alerts for the selected profile. In the case that this field is empty, notifications are sent for all the profiles.
• Recipient address – the email address or username in SAP system.
• Type – determines the notification type. Possible values are:
  • E-mail – notification is sent to the email specified in Recipient address.
  • SAP Office message – notification is sent to the SAP Business Workplace of the user, who is specified in Recipient address.
  • Private distribution list – notification is sent to all addresses defined in SAP Private distribution list (transaction SO15 or button Distribution list in Insights toolbar).
  • Shared distribution list– notification is sent to all addresses defined in SAP Shared distribution list (transaction SO15 or button Distribution list in Insights toolbar).
• BAdI ID – [optional] ID, which is used for filtering of a BAdI call. You can create your own BAdI for notification, using the BAdI implementation /DVD/MON_BADI_DEF_EVENT. For each BAdI implementation you should define the filter, which is used to determine the explicit call of the BAdI notification. Default BAdI implementation used for notifications has the initial BAdI ID.
• Alert notification – determines the period for sending notifications. Possible values are:
  • At first occurrence – notifies when an alert occurs the first time
  • At next occurrence – notifies by each occurrence of an alert
  • At end of alert – notifies when an alert is completed

^{Alert notification}