Alert classes organize alerts and specify their initial properties. Classes are groups of alert profiles like queue, escalation policy, and display attributes. Classes make it easy to define alerts because properties are automatically given to alerts in each class. You do not have to specify all alert properties manually.
Besides linking alerts to the other objects like queue and escalation policy, classes also specify properties not defined elsewhere. These include:
Urgency indicates how soon a technician or operator should try to resolve the situation that caused an alert. Because a situation can become more urgent or less urgent as time passes, you can change the urgency manually or with escalation policies after an alert is generated.
Impact indicates how much an event affects your business. A consideration in determining the level of impact is how many users are inconvenienced by a situation.
Priority is a value calculated by multiplying urgency and impact. Priority provides an additional way, besides urgency and impact, to evaluate the severity of an alert.
Consolidation groups alerts that have the same alert class, alert queue, node of origin, and alert text. Consolidated alerts appear on the Management Command Center as one alert that has a number indicating how many similar alerts are grouped together. When alerts are consolidated, fewer messages appear on the Management Command Center. Also, if the alert creates a Service Desk request, only one request is opened.
Alarm is a property that indicates an alert should be acted on promptly. Alarmed alerts attract more attention than other alerts because an Alarm dialog is displayed on your desktop.
(Optional) A calendar indicates the dates and times when alerts in a particular class can be created.
(Optional) Expiration date is a date when alerts in a particular class will no longer be created. On this date, the class is deactivated.
|
Copyright © 2010 CA.
All rights reserved.
|
|