Viewing abnormalities in the operator console
The Abnormalities> Events View lists all abnormality events for groups, services, devices, and monitors monitored by Infrastructure Management.
Using the operator console to complete IT Operator goals
Monitoring and managing events from the operator console
Adding a column to an event list for an abnormality in the operator console
Deleting a column from an event list for an abnormality
Filtering event display for All Abnormalities
Viewing further information for an abnormality in the operator console
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:
|
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. |
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:
|
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.
Comments
Log in or register to comment.