Managing Project-Level Downtimes

You can apply downtime windows to an individual schedule associated with an individual API call you're watching or to all your API calls. During the defined downtime window, calls will not run.This is useful if you're planning a maintenance window, and you don't want to flag failed calls during a planned downtime.

📘

Organization-level downtimes

This page provides instructions to manage downtimes on a per-project basis, which is available to customers on Starter, Teams, Pro, and Enterprise tiers. Pro and Enterprise customers also have the ability to manage downtimes for the entire organization. Instructions on managing organization-level downtimes via API are here: https://docs.apimetrics.io/reference/create-org-level-downtime

To implement a Downtime for your Schedule, select the Add Downtime button for the desired Schedule.

This will bring up a popup where you can set the date and time for the start and end of your downtime and the timezone. This downtime can also be set to repeat daily or weekly.

📘

Downtime is set during "standard time," not daylight savings adjusted times

When you set your downtime, it will use the standard "winter" timezone and respect locales, meaning it will automatically change for DST.

Once your done, select the Save changes button.

🚧

Downtime will apply AFTER the last scheduled call has been executed

You might want to schedule some time around the start of your maintenance window - the reason is calls might be scheduled in the queue before the downtime starts and the call might start inside the window. For example, if you have a downtime scheduled to start at 12:00, and a monitoring call also scheduled for 12:00, the call will complete before the downtime begins.

Suspending Alerts

If you would rather leave the calls scheduled, you can turn off the alerts for the period of downtime - this currently has to be done per alert and per project.