> 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/user-guide/monitoring/general/maintenance-mode.md).
# Maintenance Mode
Maintenance Mode (MM) suspends monitoring for all components when applied to a monitored system. It is propagated down the service tree, implying that when a Site enters MM, all its associated applications also enter MM. Similarly, when any element in the service tree enters MM, all its child elements are likewise placed in MM. Placing monitored systems in MM is primarily intended to facilitate planned outages.
* Placing the IT-Conductor Gateway (GW) in MM triggers the suspension of monitoring for all systems assigned and handled by that specific GW.
* 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.
{% hint style="info" %}
**Note:** The calculation of system availability omits the time interval during which the system is in MM, ensuring no impact on SLO/SLA attainment.
{% endhint %}
### Enable Maintenance Mode
There are several ways to enable MM for an object:
#### **Manual**
If an object supports MM, you should see an MM tool icon or find a "Maintenance On" object menu item. Initiating MM manually is logged in the audit trail and persists until the object is removed from MM, either manually or automatically.
#### **Scheduled**
Systems can be assigned a Maintenance Schedule. When the schedule is activated, the system enters MM. Similarly, when the schedule is deactivated, the system exits 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 be linked to Maintenance Events to have them placed in MM and taken out of MM on schedule.
To set this up, click on the service "Events" tool or select the "Events" object menu item. This opens a list of assigned events.
To create a new event, maximize the popup and click on the "Maintenance Event" icon. This will trigger a wizard, guiding you through the creation process and prompting input for the start and end times.
At any point, you have the option to delete or terminate the ongoing event, effectively removing the object from 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.itconductor.com/user-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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.