OMi Health Status

The OMi Health Status tab displays the health information of the OMi deployment. To ensure efficient operations, OMi keeps track of the health of its components and reports problems so that a corrective or preventive action can be taken.

OMi Health Status contains the following panes that provide the health status of OMi self-monitored components, display a list of related events and show how the health status of the selected object affects the health of the related objects in a view:

• Monitoring Dashboard - OMi Health Status

  The health status of each OMi object is displayed using the following widgets: simple status, pie, and history. Each widget references an OMi area for which the health-related information is displayed or provides an overall health status summary of all self-monitored objects.

  Widgets enable you to quickly determine the status of the monitored area by displaying a color that reflects the severity of the most critical event (for example, red for the severity critical). The number of events per severity is shown as well.

  Each widget references an event filter and a view, and only displays the status of those events that match the filter criteria and are related to the configuration items included in the referenced view. When you click a widget, the information on the related OMi self-monitored area is passed to the Event Browser and the Top View components. As a result, the Event Browser displays only the matching events and the Top View displays the view associated with the widget.

  For more information on widgets and monitoring dashboards, see Monitoring Dashboard.

  The following widget group is part of the OMi Server self-monitored area of the OMi Health Status monitoring dashboard:

  • Event Processing

    This widget displays the status information on the health of the event processing. It monitors a number of OMi log files, including the log files for the OMi Marble Status Calculation and the processing of the OMi JMS bus event queue. The events displayed in the Event Browser are created for the monitored log file entries with the severity ERROR.

  • Job Handling

    This widget displays the status information on the health of the deployment jobs. The critical events displayed in the Event Browser may relate to various job deployment issues, for example, failed policy templates transfer from the OMi server to monitored nodes, or the problems with transferring the assignment information from nodes to the server.

  • OMi Server Processes

    This widget displays the status information on the health of the OMi server processes. The events displayed in the Event Browser result from monitoring the OMi Nanny process log file, as well as from monitoring if the Nanny process itself is up and running.

    Note The OMi Nanny process monitors all processes running on an OMi system. If an OMi process fails, Nanny restarts it automatically and records this information to a separate log file.

  • OMi Server Infrastructure

    This widget displays the status information on the health of the OMi server infrastructure (resulting from monitoring the disk IO operations and space utilization of the system).

  The status indicator next to OMi Server combines all statuses displayed by related widgets. It takes the most critical status as the overall status indication (for example, if a critical issue is detected in one area, the indicator color changes to red).

  The following widget group is part of the Operations Agent self-monitored area of the OMi Health Status monitoring dashboard:

  • Agent Health

    This widget provides the status information on the health of the HPE Operations Agent. The events displayed in the Event Browser are generated from internal messages sent by the agent (they may include agent communication problems and failed processes).

  • Agent Connectivity

    This widget provides the information on the HPE Operations Agent connectivity status. The events displayed in the Event Browser are related to the agent's heartbeat checking: if no heartbeat event is received from the agent within the configured interval, an event indicating a problem is created.

  The History chart is a status-trend widget that displays the number of events per severity against time.

  The Overall chart is a pie-chart widget that gives an at-a-glance overview of the severity of all events occurred over a certain period of time. It is divided into colored status slices, each slice representing a number of events having a critical, warning, or normal state.

  Note The widget selected in Monitoring Dashboard - OMi Health Status determines which events are displayed in the Event Browser and which view is selected as the Top View.

• Event Browser

  Displays a detailed summary of the events that occur in the OMi self-monitored environment. The list of events is updated dynamically based on the widget selection in the Monitoring Dashboard - OMi Health Status. For more information, see Use the Event Browser (HTML).

• Top View

  Displays a topological view of the configuration items (CIs) affected by the events displayed in the Event Browser pane. The view shows the relationships between the CIs that represent the monitored objects and indicates their current health status. The color of an object displayed in the Top View takes the most critical status of the contributing objects: if at least one critical issue is detected, the entire CI is marked red. (The color used depends on the view settings. For example, you can set green for a normal and red for a critical state.)

  Two views that are integrated with the OMi Self-Monitoring are OMi Deployment and OMi Deployment with Operations Agent.

  For more information on the Top View, see Top View Component.