Maintenance mode and service dependencies

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. This rule applies even if you only want to put a single service in maintenance mode. For example, the following topology tree shows that Service 5 depends on Service 4, Service 4 depends on Service 3, and so on:

MWdependencies.png

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. The same applies to Service 5, which depends on the health scores of all the other services. You need to put services 1, 2, 3, and 4 in maintenance mode in order for Service 5 to be in maintenance mode.

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

For instructions to add dependencies to a service, see Add service dependencies in ITSI in the Service Insights manual.