This documentation supports an earlier version of BMC Helix Operations Management.

To view the documentation for the latest version, select 23.1 from the Product version picker.

Service health score, impact score, and metrics

The health of a service depends on the health of its entities. For example, a JIRA management service contains entities such as Incident Management, Change Management, Web server, and a database. If the Change Management system is down or its performance is highly impacted, the JIRA management service is also impacted. In a service model, each service entity is referred to as a Configuration Item (CI). 


Service entities and Configuration items are interchangeably used in BMC Helix AIOps .

The service health score and service impact score are the two most important indicators of service health. The health and impact scores provide a quick insight into service health and enable you to take timely action. 

Related topics

Event noise reduction indicator for prioritized triage and remediation Open link

Total incident count and mean time to resolve (MTTR) indicators for a reliable incidence-response process Open link

Probable cause analysis (PCA)

Service health score

The service health score is used to assess the health of a service. The service health score is computed for the selected time range using the impacted events associated with each of the service entities and the significance derived from service topology. The higher the health score, the healthier the service. The service health score ranges from 0 to 100.

In the  BMC Helix AIOps  console, the service health score is displayed on the service details page as shown in the following image:

The service health is represented using the color-coded severity values as shown in the following image:

If the service severity is Ok, the service is healthy. Any other severity value such as Critical, Major, Minor indicates that the service is impacted. 

Impacted entities and Impacted CIs

Impacted Entities on the service details page displays the top 3 impacted business services that are part of the main impacted service. In the following example, BMC Banking Application and Banking Core Servers are the top impacted business services that are part of the BMC Financial Service business service. Impacting Events shows the number of open events impacting the services. 

Impacted CIs on the Services page displays the total count of impacted CIs associated with a service. In the following example, there are 5 impacted CIs that are associated with the cattle_namespace and 2 impacted CIs with manual_bs_service services.

Service health timeline

The service health score for the selected time range is represented by using the health timeline on the service details page. Here is an annotated screenshot of the service health timeline:

  1. Time range selector. Click the arrow to change the time range. You can select a relative time range such as 3,6,12, and 24 hours. By default, Last3 hours time range is selected. Depending on the time range selected, the timeline is divided into equal-length time slots as shown in the following table:

    Time range

    Length of each time slot
    3 hours5 minutes
    6 hours5 minutes
    12 hours15 minutes
    24 hours20 minutes
  2. Service health score for a specific time slot on the health timeline. Hover over a time slot to view the health score. 

    What happens when there are different health scores in the same time slot?

    If there are different health scores in the same time slot, the latest health score will be displayed when you hover over the time slot. For example, consider a time slot between 8 PM and 8.05 PM (five minutes), and if there are 3 health scores such as 20, 60, and 50 in this time slot, the latest health score 50 is displayed when you hover over this time slot.

    The duration or length of each time slot is fixed, but the time window changes dynamically for each slot based on the current time. For example, consider the current system time is 8 PM, and you selected the Last 3 Hours option from the Health Time. In this case, the slots are plotted between 5 PM and 8 PM. Each slot is split into 5 minutes intervals starting from 5:00 to 5:05 PM and ending at 7:55 to 8:00 PM. If the same Health Time line is viewed at 8:01 PM for the last 3 hours, the range starts from 5:01 to 5:06 PM and ends at 7:56 to 8:01 PM.

    Therefore, the slot length or duration is maintained constantly (see Time range) based on the duration selected, but the time window for the slot changes dynamically based on the current selection and system time.

  3. Legends to indicate incidents, events, and change requests on the health timeline. Hover over a legend on the health timeline to view event, incident, or change request details. For more information, see:

    How do I derive insights using the event, incident, and change request legends?

    When you hover over a legend on the health timeline, the corresponding details are displayed along with the timestamp. If you find unusual occurrences of events, incidents, or change requests, hover over the legends, collate the details, and analyze them to resolve the issues.


    In the preceding example:
    The event count is 1 on 15/02/2021 at 12:37, and the event count is 10 on 15/02/2021 at 13:32. You can check the details of the events that occurred during this time slot and analyze the associated information to determine and resolve the error condition. Click the time slot to view the event details and to perform PCA. For more information, see Probable cause analysis (PCA).

Service impact score

The service impact score indicates how the service is impacted because of its entities. The service impact score is inversely proportional to its health score. The higher the service impact score, the lower is its health.
Impact score = 100 - service health score

The service impact score is displayed on the service details page as shown in the following image:

The service health score is 90 in the example and hence the impact score is 10.


Metric is an important performance indicator in your environment. For example, if you have a Linux monitoring solution and CPU monitor type, the following section lists a few example metrics that can be monitored:

  • Utilization
  • Load
  • Idle time
  • Context Switches

You can view the metrics associated with the top three events associated with the top 3 impacted nodes for a service. An example metrics chart is shown in the following image:

Where to go from here

Monitoring services

Was this page helpful? Yes No Submitting... Thank you