(DI-2205) Set up an Alert with a Threshold

Some of the KPIs have predefined alert(s) with thresholds. You might find the list of all available alerts in (DI-2205) Alert Definition. If you want to set a new alert or change the existing threshold values of an existing alert, you need to use the (DI-2205) KPI Tree and Context Menu 

Set threshold

Set threshold helps you to create a new alert definition for a KPI. To better understand how the alerts work, please check the (DI-2205) Set up Alerts.

You can define only a new threshold for a KPI which is currently monitored at least on one system. If this KPI is not monitored at all, you can not set a new threshold (you need to start the monitoring of this KPI first). If the selected KPI is already monitored and does not have any alert assigned yet, the following item will display in the KPI Context menu (by selecting the relevant KPI from the context menu in the KPI tree).

When item 'Set threshold' is selected, the following pop-up with some predefined values is displayed:

  • Description - description of the alert which is displayed when the alert is triggered. 
  • Alert typedefines the type of an alert. 
  • Raise alert when - operator which is used to compare the KPI value and when this condition is met, the alert is raised. 
  • For system - you might specify a system to which is this alert suitable. If no system is provided (empty value), the alert is applied to any system. 
  • Checking period time - defines the frequency in minutes. This frequency defines after which time is the alert evaluated again. 


You might set a long description of this alert through the button Long Description and enter a custom text as a description.

Additionally, you might set also the recipient(s) for the (DI-2205) Alert Definition when the alert is triggered. 

When you set a new threshold value and save it, a new alert definition is created in the customizing for the selected KPI. All alerts which are generated via this context menu have the following name: X<KPI_NAME(21)><(NUMBER(10)> (e.g., XCPU_SYS0000002002). 

Change threshold

You can change the existing threshold only for a KPI which is currently monitored at least on one system. If this KPI is not monitored at all, you can not change the threshold (you need to start the monitoring of this KPI first). If the selected KPI is already monitored and has already assigned any alert, the following item will display in the KPI Context menu (by selecting the relevant KPI from the context menu in the KPI tree).


When item 'Change threshold' is selected, the existing thresholds are displayed in the sub-menu. There are two types of thresholds:

  • General settings -  general settings represent the threshold that is suitable for any system (no specific system is defined for this threshold). 

  • System specific settings - the name of the specific system displayed in the submenu. This item means that the threshold is suitable only for this specific system. 

In case that one alert has more than one threshold defined, all existing thresholds are displayed in the following format "<Alert_type>: KPI <operator> <threshold_value>" (for example "W: KPI > 5").

If you want to create a new alert with a new threshold value beyond the existing one, you can select the item 'New settings'. The functionality is the same as mentioned above in the chapter Set threshold.   

You might change these existing threshold values by selecting any relevant record which you would like to change. When you change a threshold value and save it, the existing threshold is updated in the customizing. 

Deactivate threshold

If you want to deactivate any threshold for any existing alert, you need to select any existing threshold as described in the chapter 'Change threshold'. When the threshold is selected, the following pop-up is displayed.  

In this pop-up, there is an additional button 'Deactivate' which will adjust this threshold validity (this threshold is marked as not valid as of a time when it was deactivated). When the threshold is deactivated, it is not used anymore in the alerting functionality.