For a Service relying on Shared-Base-Searches to populate KPIs, the KPI results in the Service Analyzer are not complete. In particular, an entity that is supposed to be part of the service is not showing up in the "per entity" results panel for the KPI.
In the ITSI Healthcheck page, the impacted entities are listed as duplicate in the duplicate entities detection panel.
Analysis to confirm the behavior:
Go to ITSI > dashboards > ITSI health check page, scroll down to the Check for Duplicate Entity Aliase panel . If the list if long, open the populating search. Check if the impacted entities are listed as duplicate.
See documentation Configure: Healthcheck
Once you identified the entities, go to "configure > entities management" and search for the entities, confirm that you have more than one entity matching the title / host name. And open the editor to check the alias fields that are duplicated, and the entity_types.
The cause is that because the entities filters have more than one entity possible in the entity lookup, the filter will only pick one of them randomly.
When the Shared-Base-Search applies the entity_filter, the entity returned may not be the one that is matching the fields in the events data, or in the info and alias fields in the lookup. Therefore when the Shared-Base-Search last grouping step is trying to match each entity to each service, it fails to associate the results to the KPI.
Another possible issue is that the entity returned are not matching the data, if the entity_types are different, and alias fields are expecting a specific case (for metric format data).
When using an Ad-Hoc KPI search, as the entity filter is not applied at the same level, the entities usually stay in the results as they is not extra grouping step.
Note: Putting the extra duplicates entities in "maintenance mode". or in "retired" mode will not solve the problem. They need to be deleted
To merge manually an entity :
After fixing the entities, wait for the KPI to execute it's next run, and validate in the Service Analyzer that the KPI shows data for the remaining entity.
To prevent duplicates to be created :
If the duplicates are caused by import logic issues, you may want to also fix your entity import searches and entity import methods, to prevent this.
For ITSI implementation help, you can reach your account team for "Professional Services", or open a "On Demand Services" request on the splunk.com support portal.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
30-Sep-2026
|
Initial Release |