Configuring anomaly-based alerts/exceptions
Follow these steps to include a workload in the reporting of anomaly-based alerts/exceptions.
About this task
Anomaly detection is specified at the monitoring profile level, with each profile monitoring a specific workload type. When anomaly-based exceptions are enabled, the following occurs when a query workload matches the profile:
- DB2® Query Monitor calculates the mean and variance for the specified attributes (CPU, Elapsed, Get Pages)
- The mean will be maintained through intervals and per interval
- More recent executions will be weighted more heavily
- Users will specify a sensitivity value to control how far from normal before triggering the alert or exception
- Properly specifies the workload (plan, program, etc.)
- Excludes any SQLCODEs from exception reporting for the workload
- Defines an exception limit greater than 0
- N in the Threshold Exceptions field.
- N in the Threshold Alerts field.
- Y in the appropriate Anomaly-based Exceptions fields (CPU Anomalies, Elapsed Anomalies, Getpage Anomalies) along with an appropriate value in the Toleration Level field for each of the selected fields.
- Y in the appropriate Anomaly-based Alerts fields (CPU Anomalies, Elapsed Anomalies, Getpage Anomalies) along with an appropriate value in the Toleration Level field for each of the selected fields.
- Discard above (sigmas) values for the selected fields (CPU Discard Level, Elapsed Discard Level, Getpage Discard Level)
- All work is excluded from exception reporting until a filter is set up to specifically include it.
- It is recommended that you name your workload by filling in the optional Workload Name field on the Insert (or Update) Profile Line panel to facilitate the identification of the monitoring profile line and workload with which captured activity is associated.