Defining Thresholds and Notifications

Thresholds are the key parameters, which help to classify whether a collected monitoring parameter should be in alarm state, or not. Thresholds can be defined for any of the collected parameter. To define a threshold from the performance view, perform the following steps.

1. Select ‘Performance’ then click ‘Server View’. In the ‘List View tab click the host for which threshold has to be defined. The details of the device will be displayed.

2. Select the monitoring parameter for which the threshold needs to be defined. (Disk/CPU etc)

3. On the top-left corner of each graph click the ‘ ’ icon. The threshold window will be displayed.

4. Enter the threshold details in the window and click ‘Save’ button.

Defining Threshold

Sr. No	Field Name	Description
1	Threshold Caption	The Caption with which the threshold would be referred.
2	Alert Message	The custom alert message that would be displayed with the actual alarm message that the threshold would generate.
3	Should Not Exceed	Select this radio button option if the collected value 'should not exceed' the threshold value that is to be defined.
4	Should Not Lag	Select this radio button option if the collected value 'should not lag' the threshold value that is to be defined.
5	Info	Define the threshold value; if the actual collected value breaches [exceeds/lags] the threshold value then 'Info' alarm is generated. Select the notification profile in the ‘Notify To’ drop down to which the fault needs to be notified.
6	Warning	Define the threshold value; if the actual collected value breaches [exceeds/lags] the threshold value then a 'Warning' alarm is generated. Select the notification profile in the ‘Notify To’ drop down to which the fault needs to be notified.
7	Error	Define the threshold value; if the actual collected value breaches [exceeds/lags] the thresholds value then an 'Error' alarm is generated. Select the notification profile in the ‘Notify To’ drop down to which the fault needs to be notified.
8	Generate Ticket	Select the profile which is to be used while submitting a ticket when the threshold breach happens. Note: This profile is created in the 'Service Request Integration' section in 'Fault Management' chapter.
9	Tolerance Count	The tolerance count that needs to be applied whenever a threshold breach happens. This helps to discount any occasional irrelevant spikes in the monitored parameter to be classified as an alarm. No alarm would be generated if the breaches happen within the tolerance count range.
10	Availability	This is enabled only for the 'Availability' statistics. For such statistics all other threshold formulae inputs are disabled, and only this field is enabled.
11	Don’t suppress consecutive alerts	If this is checked, then an alarm is generated for each threshold breach [even if it was found to be in a breached state earlier]. This results in many alarms for the same state. For instance if the CPU utilizations value of a device breaches a threshold condition, then the alarms would get generated for each poll value, until the CPU utilizations is well below the set threshold limit

Note: Thresholds can be defined for all the views in a way similar to ‘Server View’ as explained above

Threshold and alarm notifications are explained in detail the chapter ‘Fault Management’. Threshold defined through this screen will be applicable for the device/ instance/statistic that is viewed in the chart (for instance for the device demo/ for instances C:, D:, E: and for the statistic disk utilization)

For defining the thresholds globally (applicable for all the resources) click ‘Settings’ then from the ‘Log Monitoring and Fault Management’ section click ‘Built-in Thresholds’ option. This is discussed in detail in ‘Fault Management’ chapter

Notification profiles can be defined using the ‘Settings’ then ‘Log Monitoring and Fault Management’ and then 'Notification Profiles’

[ Home | Top of page | Previous Page | Next Page ]