Maintenance Mode applies to many IT-Conductor components and is used to temporary disable this component functionality

When a monitored system is put in Maintenance Mode (MM) monitoring of all system components is suspended. Planned outage is the primary intended use for MM for monitored systems

System Availability Monitoring - when the system is in MM the calculation of availability excluded the time interval the system is in MM thus there is no impact on SLO/SLA attainment.

Maintenance Mode is propagated down the service tree, meaning if a Site is put in MM, all applications in the site will also go into MM, conversely if any service tree element put in MM all its children are also put in MM

When IT-Conductor Gateway (GW) is put in MM , due to the fact that monitoring systems assigned and handled by a specific GW, all system assigned to that GW are also put in MM

When Threshold Overrides are put in MM, in that case they are effectively disabled

When Schedules are put in MM, all scheduling is suspended

When Object Templates are put in MM, the templates triggering is suspended

When User, Group or Role is put in MM, the notifications are not sent to this recipient

Initiating Maintenance Mode

There are several ways to initiate MM for an object:

When Maintenance Schedule is assigned any manual or derived MM is ignored and overwritten