Configure indexes in ITSI
IT Service Intelligence (ITSI) implements custom indexes for event storage. All ITSI indexes are listed in
- In a single instance deployment, the installation of ITSI creates the indexes in the default path for data storage.
- In a Splunk Cloud deployment, customers work with Splunk Support to set up, manage, and maintain their cloud index parameters. See Manage Splunk Cloud indexes in the Splunk Cloud Admin Manual.
- In a distributed deployment, create the indexes on all Splunk platform indexers or search peers.
For detailed examples of configuring indexes, see indexes.conf.example in the Splunk Enterprise Admin Manual.
The following table describes the indexes available in
||Stores the results of scheduled KPIs searches. Summary indexing lets you run fast searches over large data sets by spreading out the cost of a computationally expensive report over time.|
||An internal index used to support trending and cohesive anomaly detection in ITSI.|
||Stores active raw notable event data.|
||Stores all audit events for episodes, including actions, comments, status change, and owner change.|
||Stores episode metadata (tags and comments) that has been moved from the KV store after a default 6 month retention period, which begins when you close an episode in the UI. Moving data from the KV store removes extraneous data and helps improve performance.|
||Stores active episode data.|
||Stores events coming in from SNMP traps. For more information, see Ingest SNMP traps into ITSI.|
Install IT Service Intelligence in a search head cluster environment
Configure multiple ITSI deployments to use the same indexing layer
This documentation applies to the following versions of Splunk® IT Service Intelligence: 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.3.0, 4.3.1, 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.4.4, 4.4.5