Fixed issues in Splunk IT Service Intelligence
This version of IT Service Intelligence was released on September 28, 2023 and includes fixes for the following issues. Issues are listed in all relevant sections, so some issues might appear more than once.
Adaptive Thresholding
Date resolved
|
Issue number
|
Description
|
2023-08-21 |
ITSI-31404 |
Applyat command is less performant than itsiat command
|
Deep Dive
Date resolved
|
Issue number
|
Description
|
2023-08-24 |
ITSI-31471 |
ITSI timepicker modifies the timerange for users that are using non default timezone
|
2023-08-17 |
ITSI-31640 |
Deep Dive overlay values are overlayed with the unit making it hard to read
|
Maintenance Window
Date resolved
|
Issue number
|
Description
|
2023-07-25 |
ITSI-31345 |
Since upgrade ITSI to 4.17.0, filtering service at maintenance windows does not work.
|
2023-07-10 |
ITSI-31195 |
maintenance window time setting issues
|
Service Analyzer
Date resolved
|
Issue number
|
Description
|
2023-08-24 |
ITSI-31471 |
ITSI timepicker modifies the timerange for users that are using non default timezone
|
2023-07-10 |
ITSI-31097 |
In SA page filter service dropdown scroll is going in infinite loop
|
2023-05-30 |
ITSI-30080 |
Newly added entities in environment do not get linked to the services and their respective KPIs in ITSI v4.17.0
|
Service Definition
Date resolved
|
Issue number
|
Description
|
2023-08-14 |
ITSI-31692 |
KPI cloning is not working when user select KPIs from more then one service.
|
2023-08-03 |
ITSI-31556 |
Entity detail is missing data when viewing from Service Definition view
|
Service Health Score
Date resolved
|
Issue number
|
Description
|
2023-08-02 |
ITSI-31329 |
Health score calculation - Importance level is not being saved
|
Predictive Analytics
Date resolved
|
Issue number
|
Description
|
2023-08-24 |
ITSI-31471 |
ITSI timepicker modifies the timerange for users that are using non default timezone
|
Uncategorized issues
Date resolved
|
Issue number
|
Description
|
2023-06-22 |
ITSI-30946 |
Upgrade to ITSI 4.17.0 fails when the management port is changed from the default value of 8089
|
Feedback submitted, thanks!