Applicability
Splunk IT Service Intelligence 4.13.0
Splunk Enterprise
Splunk Cloud
Description
Service Analyzer score sometimes does not reflect all entities.
Investigation
RCA - This issue is due to the large number of entities(around 8000) linked to single base search, and that’s why these entity filtering rules are extensive. When adding a new entity to the service and trying to update that entity rule, create a regex filter to fetch all linked entities it is getting too large, which fails, and due to this entity filtering rule is not getting updated.
Resolution
To fix this issue, perform the below workaround:
Create three clones of the base search SAIC-ITSI-EVENTS: Critical Events and service template Critical Notable System Event Template
Now, after cloning, below base searches with the same config exists:
SAIC-ITSI-EVENTS: Critical Events
SAIC-ITSI-EVENTS: Critical Events-2
SAIC-ITSI-EVENTS: Critical Events-3
SAIC-ITSI-EVENTS: Critical Events-4
The below service templates:
Critical Notable System Event Template
Critical Notable System Event Template-2
Critical Notable System Event Template-3
Critical Notable System Event Template-4
Update reference of KPI base search to newly cloned base search in the cloned service template. Initially, all cloned service templates will be pointing to the exact base search. SAIC-ITSI-EVENTS: Critical Events. Need to update KPI in such a way that after the update, see the below configuration:
Critical Notable System Event Template → SAIC-ITSI-EVENTS: Critical Events
Critical Notable System Event Template-2 → SAIC-ITSI-EVENTS: Critical Events-2
Critical Notable System Event Template-3 → SAIC-ITSI-EVENTS: Critical Events-3
Critical Notable System Event Template-4 → SAIC-ITSI-EVENTS: Critical Events-4
Now update services to link to different clone templates. With around 136 services linked to Critical Notable System Event Template, need to divide these services equally among all cloned templates.
To update the service template linking of any service, go to the service lister page, click on Edit, and select the Link to Service Template option.
Select any cloned templates in Choose a template to link to the dropdown.
In the Update service entity rules dropdown, select the Keep existing service rules option.
Click on the Link button. This will update the service template linking to the updated template.
Update linking of existing service in such a way that all the cloned templates have the same entities.
After applying this workaround, any missing entities should be visible in the service analyzer.
Revision History
| Revision |
Publish Date |
Comments |
1.0 |
29-Sep-2026
|
Initial Release |