(DI-1805) Alert Definition

Definition of alerts

There are three options how to define an new alert.

1. The simple one is to use the context menu of a KPI and choose to create an alert.

2. The second option is to define alerts in monitoring customizing by selecting KPI from KPI defintions and choosing the option Assign alerts. There you can create new entry for an alert definition or edit an existing one. You can create only an alert of the threshold kind. For each newly created alert you must define at least one threshold value.

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

_{Alert view}

This definition consists of:

• Alert name and description – Please note that you can create or modify only field names (in this case the alert name) that start with Z*, Y* or X*. The standard customizing (field entries except the ones starting with Z*, Y*, X*) can not be changed or added.
• KPI name and description – this description will be used as the label in outputs.
• Alert type – describes the type of alert and determines the icon to be displayed if the alert occurs. Possible values are:
  • Success – 
  • Warning – 
  • Issues – 
  • Error - 
• Period time – the frequency that specifies how often the alert is rechecked.
• Changelog

For every alert created, it is necessary to define associations to the KPI and to the Profile. This can be done in the Threshold setup or Anomaly view category of this screen, according to the type of alert. 

The following fields should be filled:

• Monitoring profile – alert will be checked only for this profile under running Collector job.
• KPI name – alert will be checked only for the value of this KPI.

Comparison operator – determines in which case a KPI value causes an alert to occur.

_{Comparison operator}

• Threshold – determines the limit value for a KPI. This alert will occur if the KPI exceeds its defined threshold of associated alert.
• Unit – determines the unit of measurement to be used, i.e. %, MB etc.
• Duration start – how long can a KPI value exceed the threshold (in grey area) before an alert will occur (starting delay for alert).
• Duration end – how long a KPI value has to be outside of the threshold area (in grey area) before an alert will be stopped (ending delay for alert).

_{Treshold setup}

Each alert occurrence can be notified by email or by message in SAP Business Workplace. That can be done in the Alert notification category of this screen. The following fields should be filled:

• Monitoring profile
• Recipient address – the email address or username from SAP system can be specified.
• Type of notification – determines the notification method. Possible values are:
  • E-mail – notification will be sent to the email specified in "Recipient address" field.
  • SAP Office message – notification will be sent to the SAP Business Workplace for user who is specified in "Recipient address" field.
  • Private distribution list – notification will be sent to all addresses defined in SAP Private Distribution List (transaction SO15 or button "Distribution list" in Insights toolbar).
  • Shared distribution list– notification will be sent to all addresses defined in SAP Private Distribution List (transaction SO15 or button "Distribution list" in Insights toolbar).
• BAdI ID – [optional] ID, which will be used for filtering of BAdI call. You can create your own BAdI for notification using BAdI implementation /DVD/MON_BADI_DEF_EVENT. Each BAdI implementation has to define the filter, which is also used for determining explicit call of the BAdI for processing of notification. Default BAdI implementation used for notification has initial BAdI ID.
• Alert notification – determines the period for sending of notifications. Possible values are:
  • At first occurrence – notify when alert occurs first time
  • At next occurrence – notify each occurrence of alert
  • At end of alert – notify when alert is completed

^{Alert notification}