#SPLUNK ITSI MAINTENANCE REST API WINDOWS#

If the entity has no KPIs running searches against it, there is no impact on service health scores.Search results from KPIs in maintenance mode don't count when looking back at past data to calculate threshold values.Ĭonsider the following when you put an entity into maintenance mode:

#SPLUNK ITSI MAINTENANCE REST API WINDOWS#

Maintenance windows don't affect adaptive threshold calculations.ITSI ignores search results from KPIs in maintenance mode for the purpose of service health score calculation for the duration of the maintenance window.All KPIs within that service are automatically put into maintenance mode.Maintenance windows can have an impact on associated KPIs, service health score calculations, and other ITSI features.Ĭonsider the following when you put a service into maintenance mode: You need to put services 1, 2, 3, and 4 in maintenance mode in order for Service 5 to be in maintenance mode.įor an explanation of how dependencies are visually represented in the service tree, see Use the Service Analyzer tree view in ITSI in the Service Insights Manual.įor instructions to add dependencies to a service, see Add service dependencies in ITSI in the Service Insights manual.

The same applies to Service 5, which depends on the health scores of all the other services. If you want to put Service 3 in maintenance mode, and it depends on the ServiceHealthScore KPI of services 1 and 2, then those services must be put in maintenance mode as well. For example, the following topology tree shows that Service 5 depends on Service 4, Service 4 depends on Service 3, and so on: This rule applies even if you only want to put a single service in maintenance mode. If you want a service to be in maintenance mode, you need to put all services it depends on in maintenance mode as well, if their ServiceHealthScore KPIs are included as dependencies. Maintenance mode and service dependencies For more information, see Maintenance Services Interface in the IT Service Intelligence REST API Reference manual. Use this interface to perform CRUD operations on maintenance windows in your environment. The Maintenance Service Interface encapsulates operations on maintenance windows in ITSI.

Manage maintenance windows through the REST API For instructions on putting a service or entity into maintenance mode, see Schedule maintenance downtime in ITSI. Maintenance windows apply to services and entities. The 15- to 30-minute time buffer is a rough estimate based on 15 minutes being the time period over which most KPIs are configured to search data and identify alert triggers. This gives the system an opportunity to catch up with the maintenance state and reduces the chances of ITSI generating false positives during maintenance operations.įor example, if a server will be shut down for maintenance at 1:00PM and restarted at 5:00PM, the ideal maintenance window is 12:30PM to 5:30PM. It's a best practice to schedule maintenance windows with a 15- to 30-minute time buffer before and after you start and stop your maintenance work. This state is intended to silence alarms about machines that don't require active monitoring. Keys for the KPIs to delete.Maintenance windows allow for IT Service Intelligence (ITSI) knowledge objects to enter a maintenance state. r, -delete For input, specify a list of service keys with the Note that only existing services andĮxisting KPIs could be updated using this option.Īssumes input is available in file_path/input.json g, -get For input, specify a list of service keys with the Use this option when you want to get/create/update/delete KPIs for Is not set, the restoring will halt if duplicate names e DUPNAME_TAG, -dupname-tag=DUPNAME_TAGĪutomatically rename all the duplicated service orĮntity names from restoring with a tag. The original ITSI application version user intends to a, -conf-file Use this option when you want to back up. y, -dry-run Use this option when you want only to list objects for NOTE:Īpplicable only if importData option is used d, -persist-data Use this option when you want to persist existingĬonfiguration in KV Store during import.

However, filepath must be within quotes if Use filepath as wildcard to upload data from more than When importing data from version 1.2.0, you can i, -importData Use this option when you want to upload data to the KV Use this option when you want to perform backup/restore operations. 2 - for service KPIīackup and restore operations. Mode is set to: 1 - forīackup/restore operations. m MODE, -mode=MODE Specify the mode of operation - what kind of Input.json on entry and output.json on exit. Service KPIs, this is a directory containing When importing backed up data of version 1.2.0, thisĬould be a file or a set of files. v, -verbose Use this option for verbose logging n, -no-prompt Use this option when you want to disable the prompt h, -help show this help message and exit bin/splunk cmd python etc/apps/SA-ITOA/bin/kvstore_to_json.py -h

Splunk itsi maintenance rest api