eG Administration

MANAGER SETTINGS - THRESHOLD CONFIGURATION This page appears when you click on the Threshold Configuration subnode under the Manager Settings node of the SETTINGS tree structure. eG Enterprise is capable of automatically computing the thresholds of performance using historical data. This auto-thresholding capability eliminates the need for determining the norms of performance manually in dynamic environments where measure values vary with time. eG Enterprise uses tried and tested statistical quality control techniques to analyze past values of the metrics, and automatically sets the upper and lower bounds for each of the metrics based on this analysis. With the help of the THRESHOLD CONFIGURATION section, you can configure the ‘past values’ to be considered for automatic threshold computations. By default, to perform the threshold computation, the values reported by a measure during each day of the last 14 days is used. This is why, the Automatic threshold computation policy is set to Daily, and the Lookback period to compute automatic thresholds is set to 14, by default. According to these default settings, the threshold for a measure for 8 AM to 9 AM on August 18, will be automatically computed using the actual values reported by that measure during 8 AM to 9 AM on each of the 14 days prior to August 18. In some environments, mandatory operations - for example, data backup operations or virus scanning operations - may occur on one/more servers once a week. This in turn may increase the activity levels on those servers during that time window. In some other environments, such routine operations may be scheduled to take place at a specific time every month. If threshold computations in such environments are based on Daily data collections, then the resulting thresholds may not reflect the weekly/monthly deviations in usage, thus causing false alerts. In such a case, you can set the Automatic threshold computation policy to Weekly or Monthly (as the case may be), and specify the number of past weeks/months to be considered for computing thresholds in the Lookback period to compute automatic thresholds. For instance, say that the Automatic threshold computation policy is set to Weekly and the Lookback period is configured as 2. In such a case, to compute thresholds for 8 AM to 9 AM on August 18, the actual measure values reported on the same day and time in the last 2 weeks will be considered - this will be 8 AM - 9 AM on August 11 and 8 AM - 9 AM on August 4. Similarly, assume that the computation policy is set to Monthly and the Lookback period is set to 2. In such a case, to compute thresholds for 8 AM to 9 AM on August 18, the actual measure values reported on the same date and time but in the last 2 months will be considered - this will be 8 AM - 9 AM on July 18 and 8 AM - 9 AM on June 18. Note: If the Monthly computation policy is chosen and the date for which thresholds are to be computed is not available in the previous month - say, thresholds are to be computed for July 31, but the previous month of June has only 30 days - then, the data collected during the last day of the previous month will be used for threshold computation. In the case of our example therefore, the data collected on June 30 will be used. Finally, click the Update button.