Maintenance Windows

Maintenance windows temporarily disable a service, including all of the integrations for the service, for a set period of time. A service disabled under a maintenance window is considered to be in maintenance mode.

No new incidents will be triggered while a service is in maintenance mode. Existing incidents will not resolve; they will remain open and continue to notify users on the expected escalation policy until manually resolved.

When a maintenance window ends the service will immediately exit maintenance mode and incidents can start triggering again.

Required User Permissions

Admin, Manager, Global Admin or Account Owner roles can manage maintenance windows.

If you're not sure what role you have, or if you need your permissions adjusted, visit our sections on Checking Your User Role or Changing User Roles.

Scheduling Maintenance

Disable a Service

From a service's page, click Disable Service, and confirm the disable prompt. This service is now indefinitely disabled; click Enable to allow incidents to trigger on this service again.

Immediately Put a Service in Maintenance Mode

  1. Go to Configuration Services
  2. Click on the name of the service you would like to put into immediate maintenance
  3. Click Schedule Maintenance in the upper right hand corner
  4. Select the timezone, start- and end-times for your maintenance window

Schedule a Maintenance Window

  1. Go to Configuration Services
  2. Click on the service you'd like to put into maintenance mode
  3. Select Schedule Maintenance
  4. Enter window start and end time and dates in dialogue window
  5. Click Create Maintenance Window

Confirm that a Service is in Maintenance Mode

  1. The Maintenance Windows tab at Configuration Services shows current, future, and past maintenance windows across all services.
  2. appears next to a service on the Services page
  3. appears next to a service on the Services page
  4. In Maintenance appears at the top of a service's individual page

Take a Service out of Maintenance Mode

  1. Go to Configuration Services
  2. Click on the name of the service in maintenance mode
  3. Click edit button in the Service Maintenance box on the righthand side of the page
  4. Change the maintenance window's end time or select End this maintenance window now

Recurring Maintenance Mode for Services

If you perform regularly scheduled maintenance that results in notifications being sent from your monitoring system to PagerDuty, you can use our API to create recurring maintenance windows in PagerDuty to prevent incidents from being triggered during these maintenance periods.

We've created a few different tools to help make this process easy for users who prefer a web UI, as well as those who would rather work in the command line:

Please note the Ruby scripts will not run as is, but require you to substitute your own values for the variables at the points indicated in the source code. Once the substitutions have been made, the script will allow you to create maintenance windows programmatically.

Other values as set in the script you may want to change also. For instance, the maintenance start and end time are 2 hours apart; please change this to adjust the length of time for the maintenance window. The script as written will also create 20 maintenance windows, separated from each other by a week's time; please adjust these values to either adjust the number of windows or the length of time between windows.

Frequently Asked Questions

Will incidents created before the service is put in maintenance mode be automatically resolved?

No; existing open incidents will remain in their current state.

Moreover, incidents will not be automatically resolved through the Events API either. Maintenance mode is like flipping the "off" switch for all integrations; no actions can be taken through the Events API for all of that service's integrations when it is in a maintenance period, or disabled.

Maintenance Windows

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.