
Set KPI importance values in ITSI
After you create your KPI, you must assign the KPI an importance value. ITSI uses the importance value, along with the KPI severity level, to calculate a service health score.
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.
For more information about how KPI importance values affect service health scores, see How service health scores work in ITSI.
Prerequisite
Before you set KPI importance values, you must add the KPI to one of your services. For more information, see Add a KPI to a service in ITSI.
Steps
- 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.
PREVIOUS Add a KPI to a service in ITSI |
NEXT Create KPI threshold time policies in ITSI |
This documentation applies to the following versions of Splunk® IT Service Intelligence: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.1.0, 4.1.1, 4.1.2, 4.1.5, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.3.0, 4.3.1, 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.4.4, 4.4.5
Feedback submitted, thanks!