Splunk IT Service Intelligence

Splunk IT Service Intelligence: How is the Importance Value for KPIs calculated that contribute to the Service Health Score?

lloydknight
Builder

It was stated in the doc that:

"ITSI includes all KPIs that have an importance value from 0 to 10 into the weighted average calculation. ITSI considers KPIs that have an importance value of 11 as a special case that represents a "minimum health indicator" for the service."

Can anyone answer me the exact calculation for this? Thanks

0 Karma
1 Solution

appache
Path Finder

Hi,
Importance of KPI's are ranged to 0 - 11, from 0-10 it will give you the simulated value of the health score and if you put it up to 11 no mater what if the KPI goes to critical stage according to the thresholds fields have been specified, health score also pops up to critical stage. if the importance is 10 and KPI is critical health score will based on all the KPI's and gives you the aggregated value. But with 11 health scores shows parallel to the KPI's threshold by not considering other KPI's. you can check the simulated severity tag which was provided right next to it.

View solution in original post

appache
Path Finder

Hi,
Importance of KPI's are ranged to 0 - 11, from 0-10 it will give you the simulated value of the health score and if you put it up to 11 no mater what if the KPI goes to critical stage according to the thresholds fields have been specified, health score also pops up to critical stage. if the importance is 10 and KPI is critical health score will based on all the KPI's and gives you the aggregated value. But with 11 health scores shows parallel to the KPI's threshold by not considering other KPI's. you can check the simulated severity tag which was provided right next to it.

ntankersley_spl
Splunk Employee
Splunk Employee

In addition, if a service has a dependency based on the Service Health Score (Service B impacts Service A not with specific KPIs but with Health Score) the impacting Service's (Service B) health score will automatically be weighted at 11 for the impacted service (Service A).

sdcalmes
Explorer

Is there any way to change this? I don't really like that they are automatically weighted at 11 for the impacted service. Especially if it is a dependency that isn't as important as other ones. Also, if there are multiple things causing issues, I'd rather see a health score based on those multiple items, instead of whichever one is lower.

This also makes the KPIs of Service A worth a lot less, or at least it seems that way.

appache
Path Finder

YES if the (service A) do not have any kpi's to consider into the service health score if the (service B) turns critical the service health score for service A will also turn critical.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to July and August Tech Talks, Office Hours, and Webinars!

Dive into our sizzling summer lineup for July and August Community Office Hours and Tech Talks. Scroll down to ...

Edge Processor Scaling, Energy & Manufacturing Use Cases, and More New Articles on ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Get More Out of Your Security Practice With a SIEM

Get More Out of Your Security Practice With a SIEMWednesday, July 31, 2024  |  11AM PT / 2PM ETREGISTER ...