Previous Topic: Introduction to Alert ManagementNext Topic: Alert Queues


Alert Properties and Extended Alert Information

CA SOI alerts contain the following properties. Some properties originate from the domain manager. Other properties (for example, service impact and number of impacted services) originate from CA SOI.

# Impacted Customers

Indicates the number of customers that the alert impacts. This number is based on the number of customers that are assigned to the service that the alert impacts.

# Impacted Services

Indicates the number of services the alert impacts based on the number of services its associated CI is included in.

Acknowledged

Indicates whether an operator has acknowledged the alert.

Assigned

Indicates the name of the operator that is assigned to the alert.

Category

Indicates whether this alert condition affects the quality or risk of the services it impacts.

Class

Indicates the class (USM type) of the CI the alert is associated with.

Date / Time

Indicates the date and time when this alert was generated.

Family

Indicates the CI class family that the alert is associated with.

Highest Customer Impact

Indicates the highest impact value that the alert causes for an associated customer.

Highest Customer Priority

Indicates the highest customer priority of a customer that is associated with a customer associated with a related service.

Is Exempt

Indicates whether the alert is excluded from impact analysis calculations.

Maintenance

Indicates whether the CI associated with the alert is currently in maintenance mode.

Name

Indicates the associated CI that the alert condition impacted.

Service Impact

Indicates the impact, which is calculated by multiplying alert severity and the significance of the CI to the service. When multiple services are impacted, the most affected service is displayed.

Service Impact Value

Indicates the impact value of the service alert. This value is always a factor of 10. The Service Impact Value displayed in the Alerts table can be different from the service impact value for the corresponding service in the Topology tab. The Topology tab displays how the child objects impacted the service.

Severity

Indicates the alert severity that the originating domain manager assigned.

Source

Indicates the domain manager where the alert originated. The format is MdrProduct_domainserver@connectorserver. For example, CA:00005_spectrohost.ca.com@spectrohost.ca.com refers to a CA Spectrum connector installed on spectrohost.ca.com monitoring a CA Spectrum instance that is installed on the same system.

Source Alert ID

Indicates the ID number of the alert in the source domain manager. Only infrastructure alerts have a Source Alert ID, because service alerts are generated in CA SOI, not from a source domain manager.

Summary

Describes the alert condition.

Ticket ID

Indicates the ID of the associated help desk ticket.

Unmanaged

Indicates whether the alert is associated with any services. An unmanaged alert does not have a service association.

User Attribute (1-5)

Indicates any configured customized values. These attributes are blank by default, but you can send values to the attributes through Event Management. You can also customize the attribute names.

You can also view the correlatable USM properties for the alert's associated CI:

Note: For more information about USM properties, see the USM schema documentation. For information about how to access the USM schema documentation, see the Connector Guide.

In addition to these properties, alerts have associated extended information such as annotations, update history, and escalation history in the Alert Details tab. This information provides a full audit trail of the manual and automated actions that are taken to help diagnose and remedy an alert condition.

Annotations

Indicates the interim steps that were taken to resolve the situation that caused an alert. These comments highlight the incident management process in real time, and they can provide information for the problem management process.

Update History

Indicates how the alert has evolved since alert creation. Updates can include changes in severity and properties (such as the acknowledged flag).

Escalation Action History

Indicates the automated actions that notify, diagnose, or remedy the problem and the results of those actions. For example, if an email notification is sent, confirmation that it was sent successfully is included. If a remote device was pinged, the results are included. Escalation history therefore provides a detailed audit trail of the automated actions taken in response to an alert condition.

Alert Queues

Show the alert queues to which the alert belongs.

User Defined Attributes

Displays the names and values of the user-defined attributes.

Most Recent Audit Trail

Provides a list of recent object actions.