Maintenance Windows

Maintenance windows let you temporarily suppress alerts for a monitor during planned work. This prevents false alerts from reaching your team when you know a service will be unavailable.

Setup Guide

1. Navigate to Settings > Maintenance and click New Window.
2. Enter a descriptive name for the window (e.g., “Database Upgrade”).
3. Select the monitor whose alerts should be suppressed.
4. Set the start and end time.
5. Optionally select a recurrence type (Daily, Weekly, or Monthly) and configure the schedule.
6. Optionally add a description with details about the planned work.
7. Click Save.

Caution

If a monitor is still failing when the maintenance window ends, a new alert will fire immediately. Make sure your maintenance work is complete before the window closes.

Recurring Windows

For regular maintenance (e.g., weekly deployments), you can create recurring windows:

Type	Description
Daily	Repeats at the same time every day.
Weekly	Repeats on selected days of the week (e.g., Tue and Thu).
Monthly	Repeats on a specific day of the month (e.g., the 15th).

Set an optional end date to stop the recurrence automatically. If no end date is set, the window recurs indefinitely.

Behavior During Maintenance

While a maintenance window is active:

• Monitors continue to run checks as normal.
• Alerts are suppressed: the escalation policy does not execute.
• The dashboard shows a maintenance badge on the affected monitor.
• Status pages display a “Maintenance” indicator instead of “Down”.

When the window ends, normal alerting resumes. If a monitor is still failing after the window closes, a new alert fires.

Public Visibility

Set the Public flag to display the maintenance window on your status page. This communicates planned downtime to your users without them seeing a false outage.

Mute vs Pause

YipYap offers two ways to silence a monitor: muting and pausing. They behave differently.

Mode	Checks Run?	Alerts Fire?	Notifications Sent?
Mute	Yes	Yes	No
Pause	No	No	No

Mute: The monitor continues running checks and alerts still fire internally, but all notifications are suppressed. This is useful when you want to track state changes without disturbing your team.

Pause: The monitor stops running checks entirely. No data is collected and no alerts fire. Use this when you are decommissioning a service or performing extended maintenance where check results are irrelevant.

Org-wide Auto-Mute

You can configure new monitors to start in a muted state by default. This is useful for teams that want to validate monitor configuration before enabling notifications. Configure this in Settings > Organization under the monitor defaults section.

Editing and Canceling

• Edit: Change the name, time, or description of an upcoming window.
• Delete: Remove a scheduled window before it starts.