Xitoring Document
Home
FAQ
Support
Register
Home
FAQ
Support
Register
  • Xitoring

    • Introduction
    • Release Notes
    • Xitoring Release Notes
    • Linux Xitogent Release Notes
    • Windows Xitogent Release Notes
    • Xitoring Mobile App Release Notes
    • Account Management
    • API Access & Automation
    • Team Management & Collaboration
    • Billing & Subscription Management
  • Getting Started

    • Getting Started with Xitoring
    • Workflows & Guides
    • Monitor Your First Server
    • Import / Migration
    • Migrate from UptimeRobot to Xitoring
    • Migrate from Pingdom to Xitoring
    • Migrate from Uptime.com to Xitoring
    • Migrate from BetterStack to Xitoring
  • Help & Support

    • FAQ & Troubleshooting
    • Glossary
  • Server Monitoring

    • Server Monitoring
    • Graphs
    • Live Statistics
    • Monitor Services
    • Auto-Triggers
  • Xitogent on Linux

    • Install Xitogent on Linux
    • Update Xitogent on Linux
    • Uninstall Xitogent on Linux
  • Xitogent on Windows

    • Install Xitogent on Windows
    • Uninstall Xitogent on Windows
    • Xitogent Service
    • Update Xitogent on Windows
    • Disk Performance (I/O)
  • Xitogent on Azure

    • Xitogent on Azure
    • Monitor Azure Linux VM
    • Monitor Azure Windows VM
  • Xitogent CLI

    • Xitogent CLI
    • Xitogent Pause/Unpause
    • Xitogent Status
    • Xitogent debug
    • Xitogent Diagnosis
    • Which data we collect
  • Xitoring CLI

    • Xitoring CLI
  • Uptime Monitoring

    • What is Uptime Monitoring
    • Monitoring Nodes (Geographic Locations)
    • What is Check
    • Auto-Discovery
    • Auto Fault Tolerance
    • Heartbeat Check
    • Ping Check
    • HTTP(S) Check
    • DNS Check
    • FTP Check
    • SMTP Check
    • IMAP Check
    • POP3 Check
    • TCP Check
    • UDP Check
  • SSL Monitoring

    • SSL Monitoring
  • Incidents

    • Incidents
    • Incident's Root Cause
    • Incidents Notification
    • Incident Notes
    • Resolving Incidents Manually
    • Incident Policy
  • Maintenance Schedule

    • Maintenance Schedule
  • Email Reports

    • Email Reports
  • Integrations

    • Integrations
    • Apache Integration
    • CoreDNS Integration
    • CouchDB Integration
    • Disk Health Integration
    • Docker Integration
    • Dovecot Integration
    • Exim Integration
    • HAProxy Integration
    • IIS Integration
    • InfluxDB Integration
    • Kafka Integration
    • KeyDB Integration
    • LiteSpeed Integration
    • MongoDB Integration
    • MySQL Integration
    • Netstat Integration
    • Nginx Integration
    • OpenLiteSpeed Integration
    • OpenVPN Integration
    • PHP-FPM Integration
    • Postfix Integration
    • PostgreSQL Integration
    • RabbitMQ integration
    • Redis Integration
    • MS SQL Server Integration
    • Supervisor Integration
    • Varnish Integration
    • Wireguard Integration
  • Notifications

    • Notifications
    • Creating Notification Roles
    • Email Integration
    • Mobile Push Notifications
    • SMS Integration
    • Phone call Integration
    • Webhook Integration
    • Integration for Slack
    • Telegram Integration
    • WhatsApp Integration
    • Mattermost Integration
    • Discord Integration
    • Google Chat Integration
    • Microsoft Teams Integration
    • Atlassian Opsgenie Integration
    • Splunk On-Call Integration
    • Pushover Integration
    • Pushbullet Integration
    • Gotify Integration
    • Ntfy Integration
    • Spike.sh Integration
    • PagerDuty Integration
    • Zapier Integration
    • AlertOps Integration
  • Status Page

    • Status page
  • 3rd Party Status Pages

    • Using 3rd party Status Pages
    • Atlassian Status Page Integration with Xitoring
    • Status.io Integration with Xitoring
    • Statuspal Integration with Xitoring
    • Instatus Integration with Xitoring
  • Dashboards

    • Main Dashboard
    • Custom Dashboards
  • Metrics

    • Metrics
  • MCP Server

    • Setup & Tool Reference

Maintenance Schedule

The Maintenance Schedule feature allows users to temporarily pause monitoring on selected servers and checks. This is useful when performing technical tasks (e.g., system updates or maintenance) to avoid false positive downtime reports. With the new recurrence feature, you can now automate recurring maintenance windows (e.g., weekly server restarts) alongside one-time schedules.

See Maintenance Management for a feature overview.


Overview of Changes

  • Legacy Form: Renamed to One-Time Type (single maintenance window).
  • New Feature: Recurring Maintenance allows scheduling periodic maintenance (e.g., daily, weekly, or monthly).

How to Create a Maintenance Schedule

Navigate to the Maintenance Schedule page from the side menu and click the Add new Maintenance Schedule button. You’ll see two schedule types: One-Time (legacy) and Recurring. Follow the steps below based on your choice:


Option 1: One-Time Maintenance Schedule

For a single maintenance window:

Fields to Fill:

  • Schedule Type: Select One-Time.
  • Start: Set a start date and time for the maintenance window. Ensure correct timezone input.
  • End: Set an end date and time. Ensure correct timezone input.
  • Description: Add a note (e.g., "OS Update").
  • Share to Status Page: Check to display this maintenance on public status pages.
  • Checks/Servers: Select specific checks, servers, or groups to pause monitoring for.

Option 2: Recurring Maintenance Schedule

For periodic maintenance (e.g., daily, weekly, or monthly):

Fields to Fill:

  • Schedule Type: Select Recurring.
  • Start: Set the first occurrence’s start time (timezone-aware).
  • End: Set the final occurrence’s end time (or leave blank for indefinite recurring).
  • Recurrence Settings:
    • Frequency: Choose Daily, Weekly, or Monthly.
    • Repeat Every: Specify interval (e.g., "Every 2 weeks").
    • End By: Optional end date for recurring schedules (e.g., "End on 2024-12-31").
  • Description: Add a note (e.g., "Weekly Backup").
  • Share to Status Page: Check to display recurring maintenance on public status pages.
  • Checks/Servers: Select checks/servers to pause (applies to all instances of the recurring schedule).

Example: Creating a Weekly Maintenance Schedule

Let's walk through an example of setting up a weekly maintenance schedule that occurs every Monday and Wednesday from 4:16 PM to 11:59 PM.

  1. Navigate to the Maintenance Schedule page from the side menu and click the Add new Maintenance Schedule button.
  2. Select Recurrence Type: Choose Weekly from the dropdown.
  3. Set Frequency: Enter "Every 1 week(s)".
  4. Choose Days of the Week: Select Monday and Wednesday checkboxes.
  5. Set Start Date: Input the first occurrence's start date, e.g., 2025-03-10.
  6. Set Start Time Range:
    • From: 04:16 PM
    • To: 11:59 PM
  7. Optional End Date: If applicable, set the final occurrence’s end date. Leave blank for indefinite recurrence.
  8. Description: Provide a description, e.g., "Weekly Server Updates".
  9. Share to Status Page: Toggle the switch if you want this maintenance to be displayed on your public status pages.
  10. Select Checks/Servers: Choose the relevant checks, servers, or groups to include in the maintenance schedule.

After saving the maintenance schedule, monitoring will automatically be paused during the specified period on the selected days of the week. You won't see any downtime, incidents, or alerts during these maintenance windows.


Last Updated: 7/27/26, 5:07 PM