Splunk® IT Service Intelligence

Administration Manual

Download manual as PDF

Download topic as PDF

Overview of maintenance windows in ITSI

Maintenance windows allow for IT Service Intelligence (ITSI) knowledge objects to enter a maintenance state. This state is intended to silence alarms about machines that don't require active monitoring.

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 gives the system an opportunity to catch up with the maintenance state and reduces the chances of ITSI generating false positives during maintenance operations.

For 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. 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.

Maintenance windows apply to services and entities. For instructions on putting a service or entity into maintenance mode, see Schedule maintenance downtime in ITSI.

Manage maintenance windows through the REST API

The Maintenance Service Interface encapsulates operations on maintenance windows in ITSI. Use this interface to perform CRUD operations on maintenance windows in your environment. For more information, see Maintenance Services Interface in the IT Service Intelligence REST API Reference manual.

Maintenance mode and service dependencies

If you want a service to be in maintenance mode, you need to put all services within that service's dependency tree in maintenance mode as well. This rule applies even if you only want to put a single service in maintenance mode. For example, in the following topology tree, Service 1 depends on Service 2, Service 2 depends on Service 3, and so on:

MWdependencies.png

If you want any of the services to be in maintenance mode, you need to put all the rest of the services in maintenance as well because they're part of the same topology tree. For example, if you want to put Service 3 in maintenance mode, services 1, 2, 4, and 5 need to be in maintenance mode as well. The same applies to Service 5, which has no direct dependencies. You still need to put services 1, 2, 3, and 4 in maintenance mode in order for Service 5 to be in maintenance mode.

Impact of services in maintenance mode

Maintenance windows can have an impact on associated KPIs, service health score calculations, and other ITSI features.

Consider the following when you put a service into maintenance mode:

    • All KPIs associated with that service are automatically put into maintenance mode.
    • ITSI ignores search results from KPIs in maintenance mode for the purpose of service health score calculation for the duration of the maintenance window.
    • Maintenance windows don't affect adaptive threshold calculations. Search results from KPIs in maintenance mode don't count when looking back at past data to calculate threshold values.

Impact of entities in maintenance mode

Consider the following when you put an entity into maintenance mode:

    • If the entity has no KPIs running searches against it, there is no impact on service health scores.
    • If the entity has one or more KPIs running searches against it, all search results from all KPIs running against that entity are ignored for the purpose of service health score calculation.
    • If a KPI is split by entity, for example if the same KPI is running against two different entities, and one entity is in maintenance mode and one is not, search results generated by the KPI running against the entity in maintenance mode are ignored for the purpose of health score calculation. Search results generated by the same KPI running against the entity that's not in maintenance mode are included as usual in the service health score calculation.
    • You can put an entity in full or partial maintenance mode without it being explicitly put into maintenance mode, if a service that contains the entity is put in maintenance mode.

Impact on dashboards

Services, entities, and KPIs that are fully or partially impacted by a maintenance window appear in a dark gray color on pages that display health scores, including service analyzers, service and entity details pages, glass tables, multi-KPI alerts, and deep dives.

SAMaintenanceWindow.png

View impacted KPIs

You can view the impact of a maintenance window on associated KPIs.

  1. Click Configuration > Maintenance Windows.
  2. Select a maintenance window to see the specific services or entities impacted by it.
  3. Click Impacted KPIs to see a list of KPIs impacted by the maintenance window. KPIs that are split by entity, and thus are currently running searches against other entities that are not in maintenance mode, are listed as partially impacted. KPIs that aren't split by entity are listed as fullyimpacted.

  4. ViewImpactedKPIs.png

Last modified on 10 August, 2020
PREVIOUS
Create teams in ITSI
  NEXT
Schedule maintenance downtime in ITSI

This documentation applies to the following versions of Splunk® IT Service Intelligence: 4.5.0 Cloud only


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters