The Service Down event is supported out-of-the-box when you install the Event Orchestration run book.
If you want to use the out-of-the-box Service Down use case, you must configure the module. For any new use case, you can choose to create a new module or update the core run book module configuration. The format for the module configuration should follow the same structure as described in the table in this topic.
The format has a hierarchical structure and is based on how a computer system can be reached at a customer site in a datacenter. To be able to add new items easily, the entire configuration is stored in an XML format.
BMC_SA_Event_Orchestration_Service_Down module configuration
| | |
|---|
| | Contains the configuration required for the Service Down use case. Define Aliases each time you want to add support for a new event. Contains the following elements: - <domain>: Contains the domain name for the servers, where the event is generated. Default domain is designated by a "*". If an event does not contain any information about the domain, the default "*" domain information is used to search for the host specific information.
- <host>: Each domain can have one or more configuration related to hosts. Default value is "*". If the event contains a host name that does not have a specific section in the configuration, default host, "*" is used. Hosts are categorized by the OS type - Windows or Unix.
- <commands>: Contains the <command> element, which specifies the commands required for the triage and remediation actions.
For the service down event, <commands> contain the command to start or stop a service. While performing triage to determine if a service is running on Windows, sc status <service name> command is used. While performing remediation to start the service, a net start <service name> command is used.
The attribute use-name-stringshall be set to false for default services so that service name from the event is used as opposed to '*' while invoking commands.
Aliases configuration
<domains>
<domain name="*">
<hosts>
<host os-type="windows" name="*">
<services>
<service name="*" use-name-string="false">
<start>
<command>net start</command>
</start>
<stop>
<command>net stop</command>
</stop>
<restart>
<commands>
<command>net stop</command>
<command>net start</command>
</commands>
</restart>
</service>
</services>
</host>
<host os-type="unix" name="*">
<services>
<service name="cdp">
<search-string>/opt/bmc/bao/8.0/primary-cdp/jvm/bin/java</search-string>
<start>
<command>/opt/bmc/bao/8.0/primary-cdp/bin/bao.sh start</command>
</start>
<stop>
<command>/opt/bmc/bao/8.0/primary-cdp/bin/bao.sh stop -force</command>
</stop>
<restart>
<commands>
<command>/opt/bmc/bao/8.0/primary-cdp/bin/bao.sh stop -force</command>
<command>/opt/bmc/bao/8.0/primary-cdp/bin/bao.sh start</command>
</commands>
</restart>
</service>
</services>
</host>
<host os-type="windows" name="win1">
</host>
<host os-type="unix" name="u1">
</host>
</hosts<
</domain>
<domain name="abc.com">
<hosts>
.
.
</hosts>
</domain>
</domains> |
