Splunk ITSI

ITSI summary index: what is the meaning of is_service_max_severity_event?

jwillaime
Explorer

Hello,

I would like to know what is the meaning of the "is_service_max_severity_event" field.

It appears that in my ITSI instance, each entry for service level KPI (is_service_aggregate = 1) has 2 event, one with is_service_max_severity_event set to 0, and the other one with it set to 1.

Can somebody explain?

Thank you in advance.

Labels (2)
Tags (2)
0 Karma
1 Solution

esnyder_splunk
Splunk Employee
Splunk Employee

,"0" if this is a normal KPI data point, "1" if it's the Max Severity event. Max severity represents the most severe KPI data point among service aggregate and all entity-level data points for a given time. Its value is random if multiple data points have the same severity. This data point exists solely for the purpose of evaluating score events. It always exists for every time, even if there's no data. There is exactly 1 event for each period of the KPI. Here's some info about aggregate (normal) vs. max severity KPI values: https://docs.splunk.com/Documentation/ITSI/latest/User/KPIvaluedisplays

The one you mentioned is the indexed field of is_service_max_severity_event. Always filter against the indexed field instead of the non-indexed version.

Summary index reference: https://docs.splunk.com/Documentation/ITSI/latest/Configure/IndexRef

View solution in original post

0 Karma

esnyder_splunk
Splunk Employee
Splunk Employee

,"0" if this is a normal KPI data point, "1" if it's the Max Severity event. Max severity represents the most severe KPI data point among service aggregate and all entity-level data points for a given time. Its value is random if multiple data points have the same severity. This data point exists solely for the purpose of evaluating score events. It always exists for every time, even if there's no data. There is exactly 1 event for each period of the KPI. Here's some info about aggregate (normal) vs. max severity KPI values: https://docs.splunk.com/Documentation/ITSI/latest/User/KPIvaluedisplays

The one you mentioned is the indexed field of is_service_max_severity_event. Always filter against the indexed field instead of the non-indexed version.

Summary index reference: https://docs.splunk.com/Documentation/ITSI/latest/Configure/IndexRef

0 Karma
Get Updates on the Splunk Community!

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...