Event Orchestration framework
Event Orchestration run book is designed to enable integration with different event sources or ITSM applications. New event types can be added as plugins in the run book.
In this release, the Event Orchestration run book can only be used with TrueSight Infrastructure Management and BMC Remedy ITSM – Incident Management and Change Management applications.
The Event Orchestration run book consists of the artifacts:
Common Event Model
Common Event Model (CEM) enables a consistent definition of an event. Using a common event model ensures that an event is received by TrueSight Orchestration in a well known format irrespective of the event source. This enables the runbook to support multiple event types and event sources without the need to change the underlying framework.
For more information about the common event model format, mappings, and to view a sample event converted into the CEM format, see Common-Event-Model-for-Event-Orchestration.
Event Orchestration framework actions
The Event Orchestration process consists of the following actions:
- Triage
- Remediation
- Validation
Triage, remediation, and validation actions vary based on the event type. For example, for a ServiceDown event type a service status is queried and a service start action is performed whereas, for an OS Disk full event type, file system usage is queried and disk clean up operations are performed.
New event types can be added by adding new modules and updating the module configuration items without changing the underlying framework.
Event Orchestration framework modules
The Event Orchestration run book consists of the following modules:
Module name | Description |
---|---|
BMC-SA-Event_Orchestration | Core module for the runbook. Contains rules, schedules, and contains the core workflows for the run book. This module contains the Process Event workflow, which invokes other workflows to apply triage and perform remediation for events configured as part of the run book. For more information, see Event-Orchestration-workflows. |
BMC-SA-Event_Orchestration_Configuration | Core module for storing configuration values for the runbook. Contains configuration data for connecting with BMC Remedy ITSM and TrueSight Orchestration. In addition, adapters required for the runbook are configured in this module. |
BMC-SA-Event_Orchestration_Service_Down | This module is specific to the service down event. Contains workflows required for triage, remediation, and validation for a service down use case. In addition, contains the module configuration specific for the service down use case. |
AutoPilot-OA-Event_Orchestration | Contains workflows that translate ITSM requests or event source requests into specific request based on the target ITSM type or event source type. |
AutoPilot-OA-Credentials_Store | Stores credentials and invocation mechanism mappings used to access target servers to perform triage and remediation actions. |
AutoPilot-OA-Common_Utilities | Contains common utilities used by the other workflows in the run book. |
AutoPilot-OA-ITSM_Automation | Contains the workflows for integrating with ITSM system such as BMC Remedy ITSM to create incidents, change, and tasks for the events. |
AutoPilot-OA-Network_Utilities | Contains utility workflows utilised for networking functions such as performing "ping" commands and so on. |
AutoPilot-AD_Utilities | Contains workflows for using base adapters such as HTTP, Windows Command Line, or SSH adapters used by the run book. |
AMP-AD-BMC_Remedy_ARS | Contains workflows for integrating with BMC Remedy ITSM by using the BMC Remedy actor adapter. |
AO-AD-BMC_ProactiveNet_Performance_Management | Contains workflows for updating notes in TrueSight Infrastructure Management (event management tool). |