Skip to main content
Splunk® IT Service Intelligence

Release Notes

Splunk® IT Service Intelligence
4.18.1
This documentation does not apply to the most recent version of Splunk® IT Service Intelligence. For documentation on the most recent version, go to the latest release.

Known issues in Splunk IT Service Intelligence

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

Adaptive Thresholding

Date filed Issue number Description
2024-09-04 ITSI-37270 Use Recommended Thresholding Configuration cannot use all backfilled events

Workaround:
While backfilling the KPI customer can set the fill data gaps option other than Template:Last available value and after backfill completes successfully they can switch the option to Template:Last available value.
2024-04-12 ITSI-35070 On few KPIs using adaptive threshold, the results from the scheduled overnight run seem very different from the preview adaptive threshold results

Workaround:
Add {{| where not isnull(alert_value)}} before Template:Applyat command in the AT search to remove the empty Template:Alert value events.

Entity Rules

Date filed Issue number Description
2024-05-06 ITSI-35571 New entities are not added to linked services even if they match the filter conditions

Notable Events

Date filed Issue number Description
2024-06-25 ITSI-36467 Investigate the ConcurrentModificationException in rules engine process

Workaround:
Update the below changes *on each SH* to disable async execution of actions in Rules Engine.
  1. There should be a param Template:Rules engine feature disabled list in the file if not available then add this param with values as given in point-3.
  2. Add the value Template:RUN ACTION ASYNC to the comma separated list of values

{noformat}rules_engine_feature_disabled_list = POLICY_EXECUTOR_ASYNC_SUB_ACTORS, POLICY_EXECUTOR_STATE_RECOVERY, SORT_NOTABLE_EVENTS, RUN_ACTION_ASYNC{noformat}

  1. Restart the Template:Itsi event grouping real time search by going to Activity → Jobs → Set filters to "All" → search Template:Label="itsi event grouping" and then stop the job. It will restart after a couple of mins
2024-06-20 ITSI-36397 Actions are not performed if the event is breaking the episode based on the timebased criteria and grouping into a new group.

Workaround:
Reset Template:Policy rules check frequency delay to 60000 under Template:$SPLUNK HOME/etc/apps/SA-ITOA/local/itsi rules engine.properties

OR

Update the action rules in the new to perform the action when Template:Number of events in this episode is less than or equals to 2 if the action is Template:Number of events in this episode is == 1

2024-06-10 ITSI-36103, ITSI-36215 NEAP action rules triggers false alert emails even though the conditions are not satisfied
2024-02-08 ITSI-34393 BDT event should not satisfy 'if episode is broken' action rule for inactive episodes

Notable Event Aggregation Policies

Date filed Issue number Description
2024-06-25 ITSI-36467 Investigate the ConcurrentModificationException in rules engine process

Workaround:
Update the below changes *on each SH* to disable async execution of actions in Rules Engine.
  1. There should be a param Template:Rules engine feature disabled list in the file if not available then add this param with values as given in point-3.
  2. Add the value Template:RUN ACTION ASYNC to the comma separated list of values

{noformat}rules_engine_feature_disabled_list = POLICY_EXECUTOR_ASYNC_SUB_ACTORS, POLICY_EXECUTOR_STATE_RECOVERY, SORT_NOTABLE_EVENTS, RUN_ACTION_ASYNC{noformat}

  1. Restart the Template:Itsi event grouping real time search by going to Activity → Jobs → Set filters to "All" → search Template:Label="itsi event grouping" and then stop the job. It will restart after a couple of mins
2024-06-20 ITSI-36397 Actions are not performed if the event is breaking the episode based on the timebased criteria and grouping into a new group.

Workaround:
Reset Template:Policy rules check frequency delay to 60000 under Template:$SPLUNK HOME/etc/apps/SA-ITOA/local/itsi rules engine.properties

OR

Update the action rules in the new to perform the action when Template:Number of events in this episode is less than or equals to 2 if the action is Template:Number of events in this episode is == 1

2024-06-10 ITSI-36103, ITSI-36215 NEAP action rules triggers false alert emails even though the conditions are not satisfied
2024-02-08 ITSI-34393 BDT event should not satisfy 'if episode is broken' action rule for inactive episodes

Glass Table

Date filed Issue number Description
2024-08-20 ITSI-37082, ITSI-37083 Duplicate search job running while opening/reloading glass table, causing slowness.

Workaround:
Upgrade to fixed version (4.19.3 or 4.20.*)

Service Analyzer

Date filed Issue number Description
2024-05-23 ITSI-35809 Could not retrieve health scores for the service tiles.
2024-05-01 ITSI-35514 For KPI configured with fill data gaps with null values and set severities for null value to be other than unknown, alert_value is not present in metric index results into service analyzer does not display lane for those KPIs

Workaround:
For the problematic KPI change the fill data gaps with Template:N/A to have some custom value or set the Template:Threshold level for the null value to Template:Unknown
2023-01-12 ITSI-28014 On Splunk Enterprise SH Cluster, Drill-down link on Service is not functional for ITSI Dev Build

Workaround:
# Workaround from the UI (easier and recommended):
    1. With an admin user, go to {{https://<URL>:8000/en-US/manager/permissions/itsi/data/ui/views/service_definition?manager_cancel_url=%2Fmanager%2Fitsi%2Fdata%2Fui%2Fviews%3Fns%3Ditsi%26app_only%3D1%26pwnr%3D-%26search%3Ddefinition%26count%3D100&uri=%2FservicesNS%2Fnobody%2Fitsi%2Fdata%2Fui%2Fviews%2Fservice_definition}}
    2. Give READ and WRITE for ITOA_ADMIN
    3. Give READ for ITOA_TEAM_ADMIN
    4. Save
    5. Refresh service analyzer page
  1. Workaround from the CLI:

Service Definition

Date filed Issue number Description
2024-09-10 ITSI-37299 Discrepancy in the "Per-Entity Threshold Value" graph
2024-04-22 ITSI-35260 Entities not displaying entity_types correctly in Service Definition page

Uncategorized issues

Date filed Issue number Description
2024-06-06 ITSI-36019 Discrepancy in time in the user_access_interface.log file
2024-05-31 ITSI-35922 events from source itsi_appserver.log are way longer than new increased TRUNCATE limit

Workaround:
Copy the below stanza in Template:Apps/SA-ITOA/package/local/props.conf from Template:Apps/SA-ITOA/package/default/props.conf and increased TRUNCATE value with Template:200000.

{noformat}[source::...(/|\\)var(/|\\)log(/|\\)splunk(/|\\)itsi*] TIME_PREFIX=^ TIME_FORMAT=%Y-%m-%d %H:%M:%S,%3N%z LINE_BREAKER =([\r\n]+)\d{4}-\d{2}-\d{2}\s SHOULD_LINEMERGE = false TRUNCATE = 100000 MAX_TIMESTAMP_LOOKAHEAD = 29 sourcetype = itsi_internal_log EXTRACT-component = ^[^\[\n]*\[(?P<component>[^\]]+) EXTRACT-sub_component = ^[^\]\n]*\]\s+\[(?P<sub_component>[^:\]]+) EXTRACT-log_level = ^[^\[\n]*\s+(?P<log_level>(?:\w+))\s+\[{noformat}

2024-04-26 ITSI-35428 Customer wants to know whether Index references needs to be changed in scripts for default ITSI indexes.
2024-02-29 ITSI-34551 Breaking event does not trigger breaking action rules
2022-03-24 ITSI-22641 Premium features disabled because the ITSI license checker is not finding all the valid licenses, when they are more than 30 licenses installed

Workaround:
If the license-master has more than 30 licenses, remove the expired ones to keep the list short.
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.

Last modified on 28 February, 2025
Fixed issues in Splunk IT Service Intelligence   Removed features in Splunk IT Service Intelligence

This documentation applies to the following versions of Splunk® IT Service Intelligence: 4.18.1


Please expect delayed responses to documentation feedback while the team migrates content to a new system. We value your input and thank you for your patience as we work to provide you with an improved content experience!

Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters