Set KPI importance values in ITSI
After you create a KPI in IT Service Intelligence (ITSI), assign the KPI an importance value. ITSI uses KPI importance values, along with the KPI severity levels, to calculate the overall service health score. A service's health score is a weighted average of the severity levels of a service's KPIs and dependencies.
Importance values range from 0 to 11. KPI importance values from 1-11 are included in the health score calculation, with 1 being the least important and 11 being the most important. KPIs with an importance value of 0 are not included in the health score calculation. The greater the KPI importance value, the greater the impact that KPI has on the service health score.
ITSI considers KPIs that have an importance value of 11 as a special case that represents a "minimum health indicator" for the service. When a KPI with an importance value of 11 reaches the critical state, the overall health score for the service turns critical, regardless of the status of other KPIs in the service.
Before you set KPI importance values you must add one or more KPIs to the service. For more information, see Overview of creating KPIs in ITSI.
- Click Configuration > Services from the ITSI main menu.
- Open the service that contains your KPI.
- Click the Settings tab. The Health Score Calculation section shows the importance value of each KPI, along with the simulated health score of the service.
- Use the slider to set the importance value for your new KPI.
- Click Save.
Notice the impact that different severity levels have on the simulated health score given the KPI importance value. Use this feature to help fine-tune your KPI importance values. The simulated health score is for preview purposes only and has no impact on actual severity-level thresholds or service health scores.
How service health scores are calculated
Each service you create in ITSI has a simulated health score. The health score is a good indicator of the status of a service and is a useful metric to display in Service Analyzer, glass tables, and deep dives. A decline in a service's health can be the first sign of an issue that might lead to an outage. ITSI continuously monitors and updates service health scores.
Service health scores range from 0 to 100, with 0 being most critical and 100 being most healthy. The health score calculation is based on the current severity level of service KPIs (Critical, High, Medium, Low, and Normal) and the weighted average of the importance values of all KPIs in a service.
Info severity level is not included in the service health score calculation.
ITSI does not directly use KPIs or health scores of dependent services to calculate a service's health score. Service health scores are calculated based on the
score_contribution value for each severity level. Score contribution values are defined in threshold_labels.conf. Do not modify these values.
For example, a service contains 2 KPIs. One KPI is Critical, so the
score_contribution value is 0. The other KPI is Normal, so the
score_contribution value is 100. Assuming both KPIs have the same importance values, the service health score will be 50.
The following formula is used to calculate service health scores:
- N = count of KPIs
- G = importance value of one KPI
- K = the score contribution of the KPI (Normal=100, Low=70, Medium=50, High=30, Critical=0)
For example, if you set KPI importance values as follows:
The service health score is calculated as follows:
Service health score = (100 ∗ 10/22) + (70 ∗ 7/22) + (30 ∗ 5/22) = 45.45 + 22.27 + 6.81 = 74.53
Impact of per-entity thresholds on service health scores
When a KPI is split by entity, if any entity has a severity level that's worse than the service aggregate severity, the service health score is impacted. K in the equation above represents the score contribution of a KPI. However, if the KPI is split by entity, the worst entity is taken as the score contribution. Therefore, while the aggregate KPI score might be 100 (Normal), one of the entities within that KPI might be 30 (High), so the overall score contribution of that KPI will be 30.
In some cases, entity severity contributions can cause the overall service health score to change significantly, while the aggregate KPI severity level changes only marginally or not at all. For example, if you have a CPU % utilization KPI that is running against three entities, and two of those entities show normal severity, while the third shows critical, the overall service health score might show critical, while the aggregate KPI severity level remains normal.
For more information about per-entity thresholds, see Configure KPI thresholds in ITSI.
Impact of service dependencies on service health scores
Any service dependencies that you add to a service will impact the service health score, based on the importance value that you set for dependent service KPIs. For more information, see Set importance values for service dependencies.
Configure KPI thresholds in ITSI
Create KPI base searches in ITSI
This documentation applies to the following versions of Splunk® IT Service Intelligence: 4.9.0, 4.9.1, 4.9.2, 4.9.3, 4.9.4, 4.9.5, 4.9.6
Feedback submitted, thanks!