> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/general/maintenance-mode.md).
# Maintenance Mode
Maintenance Mode (MM) applies to many IT-Conductor components and is used to temporarily disable the component functionalities.
When a monitored system is placed in MM, monitoring of all system components is suspended. A planned outage is the primary intended use for placing monitored systems in MM.
* **System Availability Monitoring** - the calculation of availability excludes 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 is 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 are assigned and handled by a specific GW, all systems assigned to that GW are also put in MM.
* When **Threshold Overrides** are put in MM, they are effectively disabled.
* When **Schedules** are put in MM, all schedules are suspended.
* When **Object Templates** are put in MM, template triggering is suspended.
* When **User, Group, or Role** is put in MM, notifications are not sent to recipients.
### Initiating Maintenance Mode
There are several ways to initiate MM for an object:
* **Manual** - if an object supports MM, you should see an MM tool icon or Maintenance On object menu item. Starting MM manually is recorded in Audit-trail and lasts indefinitely until the object is taken out of MM (manually or automatically).
* **Scheduled** - Systems can be assigned a Maintenance Schedule. When the schedule is "On", the system is put in MM. When the schedule is "Off", the system is taken out of MM.
{% hint style="warning" %}
**Warning:** When the Maintenance Schedule is assigned, any manual or derived MM is ignored and overwritten.
{% endhint %}
* **Event-based** - Service tree elements can have Maintenance Event(s) associated with them to have it placed in MM and taken out of MM at certain times in the future. To do so, click on the service "Events" tool or choose the "Events" object menu item. This will pop up a list of assigned events. To create a new one, maximize the popup and click on the "Maintenance Event" tool icon which will initiate a wizard for creating the event, prompting the start and end time. You can delete or terminate the ongoing event at any time, which will also take the object out of MM.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/general/maintenance-mode.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.