Splunk IT Service Intelligence version 4.1.x reached its End of Life on January 19, 2021. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see Before you upgrade IT Service Intelligence.
This documentation does not apply to the most recent version of ITSI.
Click here for the latest version.

itsi_settings.conf
The following are the spec and example files for itsi_settings.conf
.
itsi_settings.conf.spec
# Copyright (C) 2005-2018 Splunk Inc. All Rights Reserved. # This file contains attributes and values for configuring the IT Service # Intelligence (ITSI) app. # # There is an itsi_settings.conf in $SPLUNK_HOME/etc/apps/SA-ITOA/default/. # To set custom configurations, place an itsi_settings.conf in # $SPLUNK_HOME/etc/apps/SA-ITOA/local/. You must restart Splunk software to enable # configurations. # # To learn more about configuration files (including precedence) please see # the documentation located at # http://docs.splunk.com/Documentation/ITSI/latest/Configure/ListofITSIconfigurationfiles # # CAUTION: You can drastically affect your Splunk installation by changing these settings. # Consult technical support (http://www.splunk.com/page/submit_issue) if you are not sure how # to configure this file.
GLOBAL SETTINGS
# Use the [default] stanza to define any global settings. # * You can also define global settings outside of any stanza, at the top # of the file. # * Each .conf file should have at most one default stanza. If there are # multiple default stanzas, attributes are combined. In the case of # multiple definitions of the same attribute, the last definition in the # file wins. # * If an attribute is defined at both the global level and in a specific # stanza, the value in the specific stanza takes precedence.
[datamodels://<app>]
* 'app' is the ID for the app containing the datamodel. blacklist = <datamodel_names_list> * A pipe-separated list of data model external authentication interface (EAI) names (IDs) to blacklist. * NOTE: Data model names do not contain pipe characters. * The blacklisted data models will not be supported and remain hidden from the ITSI UI.
[cloud]
show_migration_message = <boolean> * Removes Cloud migration messages about deprecated files or apps from the logs because this process is done internally.
[backup_restore]
* Defines settings related to ITSI backup/restore. job_queue_timeout = <seconds> * The amount of time, in seconds, before the backup/restore job queue times out if the node owning the job has been down for too long to allow other jobs to proceed. * The minimum supported timeout period is 3600 seconds (1 hour). The system sets the timeout to 3600 seconds when a value lower than this is set. * Default: 43200 (12 hours)
[import]
* Defines limits for import behavior. import_batch_size = <integer> * The number of rows or objects that the importer should analyze before attempting a save to the KV store. * Default: 750 preview_sample_limit = <integer> * The maximum number of rows that are returned from a preview request for a pending import. * Default: 100 asynchronous_processing_threshold = <integer> * The number of rows after which the bulk importer reads and stores the inbound content so that it can be processed at a more convenient time, rather than processing it immediately.
[metric_backfill]
* Defines backfill settings. pre_calculation_window = <seconds> * The size, in seconds, of the pre-calculation window for metric backfill. * The smallest accepted value is 1. Increasing this value makes the backfill search faster, but less accurate. * Default: 1
[sai_integration]
* Defines Splunk App for Infrastructure (SAI) settings. show_detection_modal = <boolean> * Whether or not to show the Splunk App for Infrastructure integration modal when the Service Analyzer loads. * If "1", ITSI displays the integration modal. * If "0", ITSI does not display the integration modal. * Default: 1
[synced_kpi_scheduling]
disabled = <boolean> * Indicates whether KPI saved searches have a randomized schedule or the same schedule. * If "1", KPI saved searches run at staggered times throughout the scheduled interval. * If "0", KPI saved searches all run at the same time during each scheduled interval. * CAUTION: Changing this value to "0" can have a significant performance impact. KPI saved * searches are designed to run at different times to prevent the search scheduler from becoming overloaded. * Default = 1
itsi_settings.conf.example
No example
Last modified on 15 March, 2019
PREVIOUS itsi_service_template.conf |
NEXT itsi_team.conf |
This documentation applies to the following versions of Splunk® IT Service Intelligence: 4.1.0, 4.1.1, 4.1.2, 4.1.5
Feedback submitted, thanks!