The display of threshold options depends on the access type of the monitor and permission to set thresholds. You can set thresholds on a monitor only if you have write access to the monitor (user group is present in the WLS field of the CI to which the monitor is associated), and permission to set instance or global thresholds. If you select an event on which to set the threshold, and the CI to which the event belongs has write access, only then are the various threshold options displayed in the Tools menu.
If the threshold is an instance threshold and the user has permission to set instance thresholds, then the instance thresholds menu will be displayed.
Always make global threshold changes from the TrueSight console for the following reasons:
In addition, before configuring the global thresholds settings, ensure that the monitor type exists in the TrueSight Infrastructure Manager. Suppose if it does not exist at the time of configuring global thresholds and you added the monitor type later, then either restart the TrueSight Infrastructure Management Server or edit and save the global threshold settings for the monitor type again from the TrueSight console for the settings to be applied.
In the BMC Cloud Lifecycle Management environment, out-of-the-box threshold values are not set for storage and network monitor types. This is because these values are absolute values in BMC Cloud Lifecycle Management, and a range cannot be set for such values.
If you have permission to set both instance and global thresholds, both of the threshold options will be displayed.
Note that the Intelligent Event history page represents the event and the threshold on which the event was raised. If the event was generated by setting an instance threshold, and the user has instance threshold permission, then only the instance threshold option is displayed in the Intelligent Event history page.
When a user does not have permission to set thresholds (instance and global), the following changes are evident in the display:
From the Tools list, select the threshold to create based on the type of threshold (absolute, signature, or abnormality) and the level of coverage (event).
Alternatively, you can reach the threshold setting through the Options > Administration tab. Click the Edit link beside Intelligent Event Thresholds and then click Edit for the relevant monitor type and threshold type.
To set Abnormality Event thresholds, click the Edit link beside Abnormality Events.
Set threshold values for the relevant attributes by using the parameters displayed on the Edit Thresholds screen, as summarized in the following table.
Parameters for thresholds
|Enabled||Allows you to select an attribute to set its threshold value|
|KPI||Parameter value represents a key performance indicator for the application class. Most application classes have 1-2 parameters that are KPIs for the application.|
|Attribute||Name of the monitored attribute to which the threshold setting applies.|
|Severity||Severity of the event created-Minor, Major, or Critical (not relevant for Abnormality thresholds)|
|Duration||The duration (in minutes) of delay from when the threshold is violated to when an event is generated. The same duration is required to close an event, starting with the first data point where threshold is no longer violated.|
|Parameters specific to absolute thresholds|
|Comparison||This is a reference point for comparison of the actual measurements with the defined threshold values. The supported operators for comparison are >, <, ==, >=, and <=. This is available only for the Absolute Global and Instance Thresholds. For example, if you select the >= operator for an attribute and set the threshold value to 90%, events are generated when the threshold value is greater than or equal to 90%.|
The values for which events are triggered. For example:
|Outside Baseline||The baseline to associate with the threshold. This helps to reduce false events associated with latest trends. |
For example, response time may be higher during peak time. In this case, associating the response time with appropriate baseline will cover any false event. If you select Autobaseline an event is generated. Other options are Hourly, Daily, Weekly, Hourly and Daily, and All Baselines.
|Predict||Select this option to generate predictive events. For more information, see Viewing predictive events.|
|Auto Close||Clear this option if you do not want Infrastructure Management to automatically close the triggered event, when the triggered event returns to normal state. This is useful for events that have a very short duration.|
|Parameters for signature or abnormality thresholds|
|Above or Below|
Reference point for the following parameters:
|Minimum Sampling Window *||Define minimum window of time to keep raw data points that will be considered for intelligent threshold computation. Data points outside this range are usually discarded.|
|Threshold *, #||The threshold field is used as an additional constraint, which must be met for the signature event to be generated. Usually, a signature event is generated if the data values go outside the baseline range. When the threshold field is set, it additionally requires the data to be above or below the threshold value. This is useful to filter out insignificant abnormalities.|
|Absolute Deviation *, #||Deviation is a way of introducing tolerance into the baseline values. If there is a small change in baseline that is not significant for reporting purposes, deviation can be set to ignore this small change. For example, if baseline low value is 40, baseline high value is 100, and deviation is set to 2, then a signature event will be generated when the average of all data values inside the threshold duration goes above 102 or below 38. The deviation value is additive (not multiplicative) and is given in the same units being measured by the particular monitor attribute (that is #,%, bytes, milliseconds, and so on). The default value for absolute deviation is 5 units.|
|Percentage Deviation *, #||Percent Deviation has the same meaning as the existing deviation field, except that the actual value of the deviation is expressed in terms of a percent of the baseline value (rather than an absolute value).The default value for percentage deviation is 5%.|
|Suppress Event *||(Abnormality events only) If suppress event is enabled, baselines projection and abnormality detection will not happen for that specific attribute.|
Click the Advanced link to set thresholds with minimum sampling window, threshold, absolute deviation, and percentage deviation. This option is applicable only for Signature and Abnormality Event thresholds.