diff --git a/communicate/maintenance-windows/overview.mdx b/communicate/maintenance-windows/overview.mdx index 1a65f263..4bc26814 100644 --- a/communicate/maintenance-windows/overview.mdx +++ b/communicate/maintenance-windows/overview.mdx @@ -25,7 +25,9 @@ After giving your window an appropriate name, the core options you have are: ![Maintenance window schedule](/images/maintenance-schedule-3.png) -Set the **start** date and time, then choose how long the window **lasts** by entering a duration in hours and minutes. Quick-duration presets (30m, 1h, 4h, 24h) and a **Now** shortcut are available. **All times are in UTC**. The builder shows the equivalent time in your local timezone underneath as a reference. +Set the **start** date and time, then choose how long the window **lasts** by entering a duration in hours and minutes. Quick-duration presets (30m, 1h, 4h, 24h) and a **Now** shortcut are available. + +Pick the **timezone** your times are entered in. The builder shows the equivalent **UTC** time underneath as a reference. Existing windows created before timezones were introduced stay on UTC, and their schedules are unchanged. #### Setting repeats @@ -38,6 +40,15 @@ If your maintenance window repeats at a certain cadence, toggle the **repeat** o > If you schedule a window on the 31st and add a **monthly repeat cycle**, your schedule will also activate on > the 30th of the relevant months and the 28th or 29th of February depending on the leap year. +#### Timezones and daylight saving + +A repeating window keeps the **local time you entered**. A window set to 4:00 AM in `Europe/Paris` runs at 4:00 AM local all year. We shift the underlying UTC time by an hour when daylight saving starts and ends, so you never have to reschedule it. + +A clock change adds or removes an hour from the day. If your window starts inside that hour, we resolve it like this: + +- When clocks jump **forward**, that hour disappears: where 2:00 AM becomes 3:00 AM, a 2:30 AM window starts at 3:30 AM. +- When clocks fall **back**, that hour happens twice: where 3:00 AM becomes 2:00 AM, a 2:30 AM window runs at the **first** 2:30 AM, not the second. + ### Check behavior Each maintenance window lets you configure how checks behave during the maintenance period. Toggle the behaviors you need: diff --git a/communicate/status-pages/maintenance-windows.mdx b/communicate/status-pages/maintenance-windows.mdx index 7efff4d0..14321c23 100644 --- a/communicate/status-pages/maintenance-windows.mdx +++ b/communicate/status-pages/maintenance-windows.mdx @@ -34,6 +34,7 @@ In the **Status page visibility** section, turn on the toggle. This is the maste - **Show on**: select one or more status pages the maintenance should appear on. - **Services affected**: choose **All services on this page**, or pick **Specific services**. With "All services", services you add to the page later are automatically covered. +- **Show affected services**: on by default. Turn it off to publish the window without naming the services it covers. See [Hiding affected services](#hiding-affected-services). @@ -64,6 +65,16 @@ Once a window is visible, it appears on your status page in several places depen ![Public maintenance detail page showing the status, severity, affected services, and update timeline](/images/docs/images/status-pages/status-pages-maintenance-detail-1.png) +## Hiding affected services + +To announce planned work without revealing which parts of your system it touches, turn **Show affected services** off in the **Status page visibility** section. The window still appears on your status page as a general event, with its name, schedule, severity, and updates. + +With the setting off: + +- The maintenance card and its detail page list no services, and no service on the page is marked as under maintenance. +- Subscriber notifications leave out the affected services. +- Incident downtime that overlaps the maintenance counts as regular downtime in your status page uptime. + ## Posting updates to your status page A maintenance moves through a [lifecycle of statuses](/communicate/maintenance-windows/overview#maintenance-lifecycle-and-updates) (Scheduled, In progress, Verifying, Completed, Cancelled) and carries a timeline of **updates**. On a status-page window, those statuses and updates are exactly what your visitors see, and each update can notify subscribers. @@ -106,4 +117,4 @@ Turn on **Don't open incidents** in the status page visibility settings. While t This option applies only to the services covered by the maintenance on the pages it is shown on. A service that also appears on another page, where it is not under maintenance, can still get an automatic incident there. -Maintenance periods are also excluded from your status page **uptime**, so planned maintenance does not count as downtime against your services. +Incident downtime that overlaps a published maintenance period is excluded from your status page **uptime**. Windows with [**Show affected services**](#hiding-affected-services) turned off are the exception: their overlapping downtime still counts.