Structured Problem Solving

OMi streamlines the whole event management process. With centralized, consolidated information, you can create consistent, reusable, and optimized processes for event response.

You can deal with the majority of the events in your environment in a highly structured way. To help you manage events more efficiently and more effectively, you can use the following:

• Tools

  You can create tools to help users perform common tasks on CIs. When you create a tool, it is associated with a CI type, and you can run the tool from the centralized console. For example, you can run a command tool to check the status of an Oracle Database instance. The tool is assigned to the configuration item type Oracle Database. If you are managing multiple versions of Oracle Databases, where the tool requires different parameters and options to check the status of the Oracle Database processes, you can create copies of the most appropriate tool and customize them for the various Oracle versions using the duplicate feature. Each tool is then dedicated to a specific version of Oracle.

• Custom Actions

  You can automate your event management by creating actions to run on events to help solve problems and improve operator efficiency and productivity. Administrators can define a variety of custom actions for the operator to use when resolving certain types of events. Context-sensitive actions and context-specific tools can also be defined for specific circumstances. For example, you might create a set of database diagnostic tools that are designed to be used to help solve database problems.

  For guidance about script definition and creation, including sample scripts provided with the product, see the Develop section.

• HPE Operations Agent Actions

  The events received in the Event Browser from HPE Operations Agent or OM may contain event-related actions configured corresponding policy templates in OMi or in OM policies. If event-related actions exist, you can run these actions from the OMi console. Those actions can be either operator-initiated or can run automatically when an event occurs.

• HPE Operations Orchestration Run Books

  If you are already using HPE Operations Orchestration (OO) to automate operator tasks for analyzing or fixing problems, these OO Run Books can be mapped to CI types within OMi. You can launch OO Run Books in an event context from the OMi console.

  In addition to manually launching Run Books, it is also possible to configure rules to automatically run a Run Book or a series of Run Books in the context of an event.

• Dashboards

  Dashboards and charts provide additional data to help you visualize and analyze performance-related problems and trends affecting the CI impacted by an event, or any neighboring CIs. OMi performance dashboards can display metrics from HPE Operations Agent, HPE SiteScope, HPvPV, Operations Connectors, and Application Management systems.

Structured event management processes are deployed to:

• Assign incoming events automatically to users in specific user groups. Automatic event assignment significantly increases the efficiency of event management and decreases the amount of time elapsed before a response to the event is possible. Administrators can configure OMi to automatically assign incoming events immediately to available operator groups who are responsible for resolving those events.

• Start actions on events that match a specified set of criteria after a specified time. Time-based event automation rules consist of three main elements:

  • Filter defining the events to which time-based event automation rules are to be applied.

  • Time period defining the duration an event has to continuously match the rule filter to start the rule actions on that event.

  • List of actions to be started on matching events. Available actions are re-running automatic actions on events, modifying event attributes, forwarding events to external servers, assigning events to users and groups, running scripts, and running Run Books.

• Display and monitor the status of events using lifecycle management concepts. You can also see who is currently working on resolving the event, along with all other users who have already played a part in the solution.

• Document how an event is handled and solved. You can annotate the event to describe the problem resolution process, or capture domain expertise by tagging events with tips and hints that improve understanding and explain the event underlying problem.