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.
,"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" 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