Known issues in Splunk IT Service Intelligence

This version of IT Service Intelligence (ITSI) has the following known issues and workarounds.

Entities

Date filed	Issue number	Description
2024-04-11	ITSI-35019, ITSI-39692, ITSI-35068	Entity dashboard page re-renders when the entity sidebar is closed or opened.

Uncategorized issues

Date filed	Issue number	Description
2025-03-11	ITSI-39406	Episode Review result list display does always not match the last filter. Workaround: There is a race condition between the populating jobs triggered each time a filter is modified. To view results from the last filter, wait for previous jobs to complete before updating the filter.
2025-03-05	ITSI-39324	Deployed integrations in an ITSI backup are not being restored in the data_integration collection. Deployed integrations don't display in the UI, but saved searches for the integrations are saved.
2025-02-14	ITSI-39098	Glasstables slower to load on 4.19.2, after ITSI upgrade from 4.17
2025-02-12	ITSI-39083	Admin user is able to edit and delete the out-of-the-box dashboards in Entity Types.
2025-01-07	ITSI-38650	Near constant time series in a time block leads to wrong thresholding levels in preview chart Workaround: In rare scenarios an adaptive thresholding recommendation could result in some time policies where the KPI values are near constant. This results in the standard deviation to be 0 or near 0. As a result when adaptive thresholding is applied some of the thresholds levels could map to the same KPI value. This can cause thresholds levels to be rendered in the incorrect order in the preview chart. As workaround the affected time policies can be manually updated by setting the policy type to Static and adjusting the threshold level so that they are associated with different values.
2024-10-18	ITSI-37708	ITSI 4.19.* throwing python errors / warnings on Splunk 9.2.* "PkgResourcesDeprecationWarning: unknown is an invalid version and will not be supported in a future release"
2021-09-01	ITSI-18709	ITSI redirects to suite_redirect 500 Internal Server Error - because of python library isolation between apps Workaround: Step 1: Identify all the splunklib directories within the splunk apps directory using command find . -name 'splunklib' | xargs -r ls -lah. Step 2: For each directory listed in step 1, check if file six.py is present. Step 3: Copy the six.py from an existing splunklib directory into all the missing directories. Step 4: Clean the cached files using find . -name "*.pyc" -delete Step 5: Restart Splunk on the ITE Work or ITSI search head.