alertlog_policy

Alert Log Policy

Example Overview
Sample Output
Troubleshooting Tips
Broader Scope of the Example

Example Overview

AlertLogPolicy is used to control the number of alerts in the database. You can specify the Alert count, and if the number of alerts exceeds the specified count, the older alerts will get deleted from the database. This is done in order to maintain the specified count in the database.

Note : The source code will have comment statements in it, which will explain to you the different segments of the program.

Sample Output

Select Administration Tools-->Policies from the Client tree.
From the menu, choose Add Policy.
Select AlertLogPolicy and enter a name for the policy in the form that pops up (as shown below):

Click Add button and the new policy gets added and the following form pops up which contains the details:

helpURL - This field need not be changed. It points to the corresponding help file.
status - This parameter takes either of the two values, namely Enabled and Disabled. AlertLog Policies are executed, only if this parameter is set to Enabled.
groupName - Indicates the name of the group with which the AlertLogPolicy is associated.
alertLogSize - Used to specify the count to control the number of alerts in the database. If the number of alerts goes above the value specified here, the older alerts get deleted from the database.
name - Indicates the name of the AlertLogPolicy.

You can schedule the policy based on days or dates by clicking the Schedule button.

Troubleshooting Tips

For optimal performance of Web NMS, it is recommended to set the Log Size above 1000. Setting of Log size below 100 results in more database operations and client updates which has a bearing on performance.

Broader Scope of the Example

A similar policy can also be written to control the number of managed objects in the database.