Viewing abnormalities

The Abnormalities> Events View lists all abnormality events for groups, services, devices, and monitors monitored by Infrastructure Management.

Columns of event information on the Abnormalities screen

Column	Description
Status	Provides basic information about the abnormality's response activity, that is, displays the current status of the abnormality. The status of an event can be one of the following: Open Acknowledged Assigned Blackout Closed
Tools menu	For events originating from BMC Impact Manger (cell), this menu enables you to perform operations on an event, execute remote actions, perform probable cause analysis for the event, retrieve BMC Server Automation device history, and export the event. For events originating from the BMC TrueSight Infrastructure Management Server, this menu enables you to perform all the actions that you can perform on the cell events. Also, you can view graphs and parent groups, add a change entry to track the changes in your environment, and set thresholds. For multiple server deployment and BMC Atrium Explorer environments, this menu provides a launch point.
Priority	Determines which abnormality requires action first
Severity	Indicates the seriousness of the abnormality. In combination with status and priority, the severity level indicates the urgency of the need to take action. Severity is based on the comparison of metrics to defined thresholds. The severity of the abnormality event is Info (blue).
Score	Indicates how closely the event relates to the probable cause of the problem
Occurred	Displays the date and time when the abnormality occurred
Message	Displays a short description of the reason for the abnormality. It might also display the following icons: Action Result Notes Related Events
Host	Displays the name of the host on which the abnormality occurred
Object	Displays the name of the object monitoring the abnormality

Note

The Infrastructure Management administrator can set up specific user-defined rules that can help you keep track of frequent events and their causes. For instance, if you continually receive an event and you realize that the event is triggered by a recognizable pattern, you can set up rules that replace Infrastructure Management probable cause description with specific information related to that event. In other words, you can override Infrastructure Management's generic probable cause information by attaching a rule to a specific abnormality that adds known information and domain knowledge into the system.

Viewing abnormalities

Related Topics

On this page