The status of Service Monitors and any kind of Alarm can be used to drive the Operational Status of a BS. A BS is defined with the following components:
Business Service Name: A unique name used to identify the BS
Edges: A set of elements on which this BS relies which can include other BS, or Reduction Keys.
Reduce Function: Function used to aggregate the Operational Status from all the Edges. Specific functions may take additional parameters.
Attributes: Optional key/value pairs that can be used to tag or enrich the Busines Service with additional information.
Each Business Service can contain a list of optional key/value attributes. These can be used to identify or tag the BS, and may be reference in other workflows. These attributes do not affect the dependencies or the status calculation of the BS.
|Attributes can be used to filter BS in Ops Board dashlets.|
The Business Service Editor is used to manage and model the Business Services and their hierarchy. It is required to have administrative permissions and is available in "Login Name → Configure OpenNMS → Manage Business Services" in the Service Monitoring section.
|1||Create a new Business Service definition|
|2||Collapse tree view for all Business Services in the view|
|3||Expand tree view for all Business Services in the view|
|4||Reload all Business Services in the view with current Business Services from the system|
|5||Reload the Business Service Monitoring Daemon to use the Business Service definition as configured|
|6||Business Service dependency hierarchy as tree view|
|7||Show the current Business Service with dependencies in the Topology UI|
|8||Edit and delete existing Business Service defintions|
As shown in figure Managing Business Services with the Business Service Editor the Business Services can be created or changed. The hierarchy is created by assigning an existing Business Service as Child Service.