|
|
The policy framework provides some examples to guide you how to create your own policies. Also, a set of pre-built policies have been provided which you can directly make use of.
Please follow the links below to access detailed READMEs for the respective examples :
Web NMS Backup Policy : The data stored in the database of Web NMS is of critical importance and human error, system crash and other disasters can result in the loss of valuable data which could prove to be costly. To overcome any such eventuality, Web NMS provides Backup Service. As the name itself indicates, backup refers to the process of taking a copy of the data and keeping it separately. In case, any data loss occurs, the backedup contents can be restored to the database and made use of. The backup of data can be taken at any time as well as any desired periodic interval. This example explains how backup of the Web NMS system can be taken using policies.
DeviceBackupPolicy : This DeviceBackupPolicy explains how to take back up of the data of SNMP devices. In the event of loss of data due to human error, system crash or other disasters, the backedup data can be used to restore the device whose configuration is lost. This example illustrates how the backup can be taken for a MIB sub-tree on the device.
Registering Observer : You may require a notification whenever a policy is added, updated, deleted, executed or stopped from execution. This is possible by registering an observer with the policy engine.
Policy Action and Condition : Explains how to execute a policy based on certain condition.
PolicyObjectCustomizer : This is an abstract class providing the base for writing Customizer which is vital for designing your own Property form. Explains how you can plug-in your own UI for viewing PolicyObject properties.
Pre-Built Policies
AlertLogPolicy : 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.
NodeDeletePolicy : Failed Node Deletion Policy allows you to delete nodes of status major and critical in the database,that exists for more than 7 days without any change in status.
Report Generation Policy : This policy helps in scheduling Performance reports generation. It provides an UI via which you can configure which report has to be generated when.
StatsTableCleanup Policy : Data collected from devices are stored either in STATSDATA table (default table defined by Web NMS ) or in user-defined tables. Whatsoever be the case, the tables are created on a daily basis (if % was appended to table name when it was defined) . After some days, if they are not required, they can be removed from database . If not done, they will unnecessarily occupy space and may further create problems while storing new tables. Hence the best way is to perform a periodic clean up of such tables. To perform this clean up operation, Web NMS provides a Policy called StatsTableCleanup. StatsTableCleanup policy is executed periodically at the specified time. This policy accepts the input regarding the Policy from the Administrator via a form. Based on those inputs it is executed periodically.
|
|