Every configurable AEC object has a configuration wizard associated with it, which guides you through the steps necessary to configure the object. The New Policy tab displays all available policy wizards and lets you select from a list of preconfigured rules. Click the radio button of any wizard you want to work with and then click Select so that you can start defining the incoming event.
The window contains the following Policy Wizards and descriptions:
Detects the absence of an important event.
Example: When a Database Backup Started event is detected but the Database Backup Completed event is not detected within a specified time range, an alert is sent indicating that the backup failed.
Suppresses messages from systems that are down for scheduled maintenance.
Example: If software patches that require a reboot are scheduled for a particular machine, you can select an event that indicates that machine is down for maintenance. All messages coming from that machine during the specified time are suppressed.
Eliminates spike alarms when a resource has acceptable periods of peak activity.
Example: A web server is known to have surges in activity every time new content is posted. The Transient Event rule suppresses alerts caused by these surges.
Suppresses repeated similar events.
Example: A host IP device failure causes DSM to repeatedly generate ping failure events. This type of rule suppresses the redundant events, allowing only the initial failure to trigger a trouble ticket.
Raises an alert for a component based on events raised by other components.
Example: A web application requires both a database and a file server. An alert for the web application is sent if either resource reports a problem.
Raises an alert for a component based on two events raised by other components.
Example: A web application runs on a cluster consisting of two cluster nodes. An alert is sent if both cluster nodes report a problem within the specified time period.
Detects the number of times a specific event occurs within a time range.
Example: When CPU usage exceeds its threshold five times in two minutes, an alert is raised.
Raises an alert for a component based on events raised by other components and provides information on the event that initiated the issues.
Example: A switch failure causes a ping failure, which causes an agent failure.
Detects the absence of a heartbeat message within a specified time range.
Example: A heartbeat message is sent from a server to communicate that it is online. The absence of the heartbeat event from the server indicates that the server is offline.
An empty rule list; it lets you manually create a customized rule.
|
Copyright © 2010 CA.
All rights reserved.
|
|