Configuring Global Thresholds

While monitoring large environments, some tests executed by the eG agent report statistics on hundreds of descriptors. For example, the UserProfileTest reports the profile size of each and every Citrix or Terminal server user of a server. Likewise, the WinSvcStatusTest reports on the availability of each and every service of a Windows system. For such tests, storage of the threshold values for each hour for each descriptor can result in significant disk space usage in the eG database. In order to enable administrators to optimize database usage for tests that do not use the automatic threshold computation (i.e., relative thresholding) capability, eG Enterprise offers the Global Threshold Configuration page.

To access this page, click on the icon available in the Admin tab. Then, select the Global option from the Threshold sub-menu of the Alerts tile.

The Disassociated Tests list in this page, displays the tests mapped to all the managed components in the target environment. From this list, select those tests for which thresholds need not be stored in the database. For example, if the User Profile test has to be configured to not store thresholds in the database, select User Profile test from the Disassociated Tests list, click on the button, and move the selected test to the Associated Tests list. Then click on the Update button Once one/more tests are so associated, the eG manager retrieves thresholds for such tests from their configuration files, and does not store any thresholds for these tests in the eG database. As a tradeoff, the thresholds for these tests apply to all the servers being managed, and cannot be set specifically for every server or for each descriptor. Hence, the Specific Thresholds button for these tests are disabled in the eG administrative interface. Moreover, when configuring the default threshold for these tests, the threshold policy has to be either “absolute” or “none”.