From 8bfdeaef772199d766cde5aafa8f3ff8cc5b886d Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Wed, 5 Nov 2025 16:07:40 -0500 Subject: [PATCH 1/5] Initial draft of scheduled maintenance --- .../service_management/status_pages/_index.md | 25 ++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/content/en/service_management/status_pages/_index.md b/content/en/service_management/status_pages/_index.md index 32a7fe3ef39a6..6c701ceb8d59a 100644 --- a/content/en/service_management/status_pages/_index.md +++ b/content/en/service_management/status_pages/_index.md @@ -22,12 +22,13 @@ further_reading: {{< img src="service_management/status_pages/shopist_status_page.png" alt="Example status page showing service components with their current status and recent incident updates" style="width:100%;" >}} -Status Pages is part of Datadog's Incident Response suite, alongside On-Call and Incident Management. It lets your team proactively communicate **service availability** and **incidents** with customers or internal stakeholders through a shareable web page. +Status Pages is part of Datadog's Incident Response suite, alongside On-Call and Incident Management. It lets your team proactively communicate **service availability**, **incidents**, and **planned maintenance** with customers or internal stakeholders through a shareable web page. Use Status Pages to: * Share the availability of critical systems and features * Communicate service disruptions clearly during incidents +* Announce scheduled maintenance and planned downtime in advance * Reduce inbound support volume with proactive email notifications ## Configure permissions @@ -130,6 +131,28 @@ After a notice is published, the notice: You can post **updates** over time to keep users informed, and then mark the notice as **Resolved**. +## Schedule maintenance windows + + +Maintenance windows allow you to proactively communicate planned downtime or service impact before it happens. Unlike [notices](#add-a-notice) which are used for unplanned incidents, maintenance windows are scheduled in advance for infrastructure upgrades, system maintenance, database migrations, and other planned work. Proactively communicate scheduled downtime so you can keep your customers informed and lessen the load on the support team. + +### Publish a maintenance window + +1. From a status page, click **Schedule Maintenance** to open the maintenance window modal. +1. Under **Notice type**, select the "Scheduled Maintenance" tab and provide: + | Field | Description | + | ---- | ---- | + | **Title** | Clear description of the maintenance activity
*Example: Database infrastructure upgrade* | + | **Maintenance window** | Scheduled time range for the maintenance window, including start and end times | + | **Message** | Set the message that you want to automatically publish for each status update | + | **Components impacted** | One or more components that will be affected during maintenance | + | **Impact** | Expected level of impact per component during the window:
- Operational
- Degraded Performance
- Partial Outage
- Major Outage | + | **Notify Subscribers** | Toggle to send advance notification to subscribers | +1. Click **Review Notice** and click **Publish Notice**. + +After scheduling, the maintenance window appears on the status page with the scheduled time range. When the window begins, component status automatically updates to "Under Maintenance" and returns to "Operational" when it ends (unless manually overridden). You can post updates if plans change, reschedule the window, or cancel it if no longer needed. + ## Email subscriptions Email subscriptions on status pages are **double opt-in**: users must confirm their email address before they are added as subscribers. After entering an email to subscribe, a confirmation email is sent, and the subscription is only activated after the user clicks the confirmation link. From 276fefc72f3738ed005328b38ee20f3c8c5e7381 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Tue, 11 Nov 2025 12:53:49 -0500 Subject: [PATCH 2/5] Apply suggestions from code review Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com> --- content/en/service_management/status_pages/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/service_management/status_pages/_index.md b/content/en/service_management/status_pages/_index.md index 6c701ceb8d59a..7c5d39c22fe49 100644 --- a/content/en/service_management/status_pages/_index.md +++ b/content/en/service_management/status_pages/_index.md @@ -135,7 +135,7 @@ You can post **updates** over time to keep users informed, and then mark the not -Maintenance windows allow you to proactively communicate planned downtime or service impact before it happens. Unlike [notices](#add-a-notice) which are used for unplanned incidents, maintenance windows are scheduled in advance for infrastructure upgrades, system maintenance, database migrations, and other planned work. Proactively communicate scheduled downtime so you can keep your customers informed and lessen the load on the support team. +Maintenance windows allow you to proactively communicate planned downtime or service impact before it happens. Unlike [notices](#add-a-notice) which are used for unplanned incidents, maintenance windows are scheduled in advance for infrastructure upgrades, system maintenance, database migrations, and other planned work. Proactively communicate scheduled downtime so you can keep your customers informed and lessen the load on your support team. ### Publish a maintenance window @@ -146,7 +146,7 @@ Maintenance windows allow you to proactively communicate planned downtime or ser | **Title** | Clear description of the maintenance activity
*Example: Database infrastructure upgrade* | | **Maintenance window** | Scheduled time range for the maintenance window, including start and end times | | **Message** | Set the message that you want to automatically publish for each status update | - | **Components impacted** | One or more components that will be affected during maintenance | + | **Components impacted** | One or more components that is affected during maintenance | | **Impact** | Expected level of impact per component during the window:
- Operational
- Degraded Performance
- Partial Outage
- Major Outage | | **Notify Subscribers** | Toggle to send advance notification to subscribers | 1. Click **Review Notice** and click **Publish Notice**. From 96d8582badceb2bee820c73be851c65d2d1a26f9 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Fri, 14 Nov 2025 12:03:31 -0500 Subject: [PATCH 3/5] Apply suggestions from code review Co-authored-by: Yuta <49351867+ramen-yuta@users.noreply.github.com> Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com> --- content/en/service_management/status_pages/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/service_management/status_pages/_index.md b/content/en/service_management/status_pages/_index.md index 7c5d39c22fe49..a9f7074c5cfaf 100644 --- a/content/en/service_management/status_pages/_index.md +++ b/content/en/service_management/status_pages/_index.md @@ -22,12 +22,12 @@ further_reading: {{< img src="service_management/status_pages/shopist_status_page.png" alt="Example status page showing service components with their current status and recent incident updates" style="width:100%;" >}} -Status Pages is part of Datadog's Incident Response suite, alongside On-Call and Incident Management. It lets your team proactively communicate **service availability**, **incidents**, and **planned maintenance** with customers or internal stakeholders through a shareable web page. +Status Pages is part of Datadog's Incident Response suite, alongside On-Call and Incident Management. It lets your team proactively communicate **service availability**, **degradation**, and **planned maintenance** with customers or internal stakeholders through a shareable web page. Use Status Pages to: * Share the availability of critical systems and features -* Communicate service disruptions clearly during incidents +* Communicate service disruptions clearly during service degradations * Announce scheduled maintenance and planned downtime in advance * Reduce inbound support volume with proactive email notifications @@ -139,7 +139,7 @@ Maintenance windows allow you to proactively communicate planned downtime or ser ### Publish a maintenance window -1. From a status page, click **Schedule Maintenance** to open the maintenance window modal. +1. From any status page, click **Schedule Maintenance** to open the maintenance window modal. 1. Under **Notice type**, select the "Scheduled Maintenance" tab and provide: | Field | Description | | ---- | ---- | From 7d9a3571ae296e9ae221cb9c32bcea60d75b3e7d Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Fri, 14 Nov 2025 12:04:37 -0500 Subject: [PATCH 4/5] Update permissions --- content/en/service_management/status_pages/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/service_management/status_pages/_index.md b/content/en/service_management/status_pages/_index.md index a9f7074c5cfaf..2f5c23420b4e6 100644 --- a/content/en/service_management/status_pages/_index.md +++ b/content/en/service_management/status_pages/_index.md @@ -58,7 +58,7 @@ To create, update, or publish Status Pages, you must have `status_pages_settings Status Pages Notice Write
status_pages_incident_write - Publish and update Incidents. + Publish and update Notices for degradations and maintenance windows. Datadog Admin Role From d207bf83d045ea1dfa1d0bfa5f51d281e1428125 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 17 Nov 2025 09:33:25 -0500 Subject: [PATCH 5/5] Apply suggestions from code review Co-authored-by: Reagan Razon <115665609+reaganrazon@users.noreply.github.com> --- content/en/service_management/status_pages/_index.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/service_management/status_pages/_index.md b/content/en/service_management/status_pages/_index.md index 2f5c23420b4e6..0984704b6e7f3 100644 --- a/content/en/service_management/status_pages/_index.md +++ b/content/en/service_management/status_pages/_index.md @@ -139,19 +139,19 @@ Maintenance windows allow you to proactively communicate planned downtime or ser ### Publish a maintenance window -1. From any status page, click **Schedule Maintenance** to open the maintenance window modal. +1. From a status page, click **Public Notice** to open the maintenance window modal. 1. Under **Notice type**, select the "Scheduled Maintenance" tab and provide: | Field | Description | | ---- | ---- | | **Title** | Clear description of the maintenance activity
*Example: Database infrastructure upgrade* | | **Maintenance window** | Scheduled time range for the maintenance window, including start and end times | - | **Message** | Set the message that you want to automatically publish for each status update | + | **Messages** | Set the messages that you want to automatically publish for each status update | | **Components impacted** | One or more components that is affected during maintenance | - | **Impact** | Expected level of impact per component during the window:
- Operational
- Degraded Performance
- Partial Outage
- Major Outage | - | **Notify Subscribers** | Toggle to send advance notification to subscribers | + | **Impact** | Default impact per component during a maintenance window. If an incident occurs during maintenance, components can transition to:
- Degraded Performance
- Partial Outage
- Major Outage | + | **Notify Subscribers** | Toggle to notify subscribers in advance and for each automatic update| 1. Click **Review Notice** and click **Publish Notice**. -After scheduling, the maintenance window appears on the status page with the scheduled time range. When the window begins, component status automatically updates to "Under Maintenance" and returns to "Operational" when it ends (unless manually overridden). You can post updates if plans change, reschedule the window, or cancel it if no longer needed. +After scheduling, the maintenance window appears on the status page under "Upcoming Maintenance" with the scheduled time range. When the window begins, component status automatically updates to "Undergoing Maintenance" and returns to "Operational" when it ends (unless manually overridden). You can edit the messages, post updates if plans change, reschedule the window, or cancel it if no longer needed. ## Email subscriptions