Customizing health score and health status
The health score of a service is computed based on multiple contributing factors, including events, health indicators, balancing profiles, and child services. The contribution of child services to the parent service health score depends on whether health propagation is enabled for those child services.
Default health score and health status values
The maximum health score for any service is 100. The health score of an impacted service is computed based on the number of events generated for a service. A service can contain a single node, multiple nodes, or nodes of different types. The health of a service depends on the health of its nodes.
If metrics are defined as health indicators for a service, such events are also considered while computing the health score.
By default, BMC Helix AIOps considers the following values:
Source | Severity | Score Impact | Description |
|---|---|---|---|
Events | Critical | 10 | For every critical event, 10 points are deducted from 100. |
Events | Major | 8 | For every major event, 8 points are deducted from 100. |
Events | Minor | 6 | For every minor event, 6 points are deducted from 100. |
Events | Warning | 4 | For every warning event, 4 points are deducted from 100. |
Health Indicator | Critical | 20 | For every critical event caused due to metrics, 20 points are deducted from 100. |
Health Indicator | Major | 16 | For every major event caused due to metrics, 16 points are deducted from 100. |
Health Indicator | Minor | 12 | For every minor event caused due to metrics, 12 points are deducted from 100. |
Health Indicator | Warning | 8 | For every warning event caused due to metrics, 8 points are deducted from 100. |
If the service model contains only one node per configuration item, the default node score is set to the event score. If the service model has more than one node, the node score is based on the first event that impacted that node.
By default, BMC Helix AIOps considers the following values for the health status:
Lower threshold | Upper threshold | Health Status | Enabled | Description |
|---|---|---|---|---|
0 | 30 | Critical | Yes | The severity is critical for the health score range 0-30. |
31 | 60 | Major | Yes | The severity is major for the health score range 31-60. |
61 | 90 | Minor | Yes | The severity is minor for the health score range 61-90. |
91 | 100 | Ok | - | The service health is considered OK when the score is above 91. |
By default, the health status configuration is enabled for the three severities. However, if you do not want to use any of it to compute the health score, clear the Enabled check box.
For example, clearing the Enabled check box for Major and Minor allows only Critical events to be considered for computation.
Understanding the impact of child services on health score computation
By default, the impact on child services is propagated to the parent service, and the health score of the parent service reflects the combined impact of its own issues and the propagated issues from child services.
As an administrator or a service designer, you can disable the propagation of impact from selected child services based on your requirements. When health propagation is disabled for a child service, issues in that child service do not contribute to the health score or health status of the parent service.
To stop propagating the health score
By default, the health score of an impacted child service is propagated to its parent services and contributes to the parent service’s health score and health status. However, to stop this impact propagation, perform the following steps:
- Click Services and then click the service for which you want to stop propagating the health score from child services.
- From the action menu
, select Edit Service. - Click Health Profile and then click the service.
- To stop propagation from all child services to the parent service, clear the Propagate health from all child services to this parent service checkbox.
If there are no child services for a service, the checkbox is not displayed.
When this checkbox is cleared, the health score of the impacted child services is not propagated to this service. As a result, issues in child services do not contribute to the health score of the parent service.
On the Edit Service page, the
icon indicates that the health score is not propagated from the child service, and the 
icon indicates that the health score is propagated from the child service. To stop propagation from a specific child service to the parent service, click the link between the child service and the parent service, and then clear the Include this child service in the parent health calculation checkbox. When you clear this checkbox, other child services continue to contribute to the parent service’s health score computation based on their own propagation settings.
In the following example, the health scores of the Analytics Dashboard, Internal Reporting, and Batch Processing services are not propagated to the Order Processing service. However, any impact on other child services is propagated to the Order Processing service.
To customize the health score for a service
- From the Services page, click Create Service.
- Click Health Profile and then click the service for which you want to define the health score.
If you have configured the health score impact value from the Manage Service Health page, the globally defined values for all services are automatically shown in the Define Health Profile section of the service. The Use global configuration check box is enabled by default, and the global health score impact values are applied to the service. - To change the values, clear the Use global configuration check box.
- Enter the new numbers or click the up or down arrow.
For example, if you update the impact score for a Critical event to 20, 20 points are deducted from 100, and the health score is computed.
You cannot specify fractions or decimal points for the score.
- Click Save and Close.
Health score for the selected service is now computed based on the updated values. It might take a few seconds for the recomputed score to be reflected for the service.
To customize the health status for a service
- From the Services page, click Create Service.
- Click Health and then click the service for which you want to define the health status.
If you have configured the health status thresholds from the Manage Service Health page, the globally defined thresholds for all services are automatically shown in the Define Health Profile section of the service. The Use global configuration check box is enabled by default, and the global thresholds are applied to the service. - To change the values, clear the Use global configuration check box.
- Enter a number, or use the arrow keys to update the values as needed.
You cannot specify fractions or decimal points for the threshold.
- (Optional) If you do not need to compute the health score based on severity, clear the Enabled check boxes.
- Click Save and Close.
Health status for the selected service is now calculated based on the updated values. It might take a few seconds for the updated status to be reflected for the service.
Where to go from here
Based on what you want to configure for your services, perform the following optional tasks: