KPI data writes data to itsi_summary index but not to itsi_summary_metrics index after the ITSI upgrade.
itsi_summary_metrics is used for most of service insights metrics, including Service Analyzer most of the reports and alerts and everything else it's done here. (this is for metrics based)
itsi_summary is used for the rest of it, for example, glass table, deep dive, all kinds of visualization data, still uses this legacy mode. (this is for events based)
scheduler.log seems running ok these searches.
creating a new service and trying to reproduce the issue, the issue isn't there.
After upgrading ITSI to Version 4.13.x, SBS unlinked from KPIs and Service Analyzer which stopped showing results from existing objects
This is a known issue in which the workaround is to replace SA-ITOA/bin/command_set_severity_fields_v2.py from your SH with the same file from version 4.17.1.
Replace it on the 4.13.x instance. If you are on an SHcluster, you will have to put the new file on the deployer and push (with a SH rolling restart).
During the old investigation, issues seemed to be isolated to the ITSI custom search command set_severity_fields, which was returning results and causing all entities found to be attached/contributing to a single KPI.
Overall, the issue is caused by an implementation issue with Python pass-by-assignment.
As I mentioned above the suggested workaround is to use the code changes which should fix the entity / kpi calculation.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |