Skip to content

Conversation

@estherk15
Copy link
Contributor

@estherk15 estherk15 commented Nov 11, 2025

What does this PR do? What is the motivation?

Merge instructions

Merge readiness:

  • Pending GA

@estherk15 estherk15 requested a review from a team as a code owner November 11, 2025 16:32
@github-actions
Copy link
Contributor

Preview links (active after the build_preview check completes)

Modified Files

Copy link
Contributor

@iadjivon iadjivon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Esther, added some non-blocking comments on this and approved. Please feel free to bypass the edits if it does not make sense within the context! Let me know if you have any questions :)

Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com>
estherk15 and others added 2 commits November 14, 2025 12:03
Co-authored-by: Yuta <49351867+ramen-yuta@users.noreply.github.com>
Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com>
<tbody>
<tr>
<td style="white-space: nowrap;">Status Pages Settings Read<br><code style="white-space: nowrap;">status_pages_settings_read</code></td>
<td>View the list of Status Pages, the settings of each Status Pages, their Incidents, and launched Internal Status Pages.</td>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<td>View the list of Status Pages, the settings of each Status Pages, their Notices, and launched Internal Status Pages.</td>

- **Public**, the page is immediately accessible to all visitors.
- **Internal**, access is limited to authenticated Datadog users in your organization.

## Add a notice
Copy link

@reaganrazon reaganrazon Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The notice modal is going to be changed with the maintenance windows work. Since Notice has two types, "Degradation" and "Scheduled Maintenance" maybe the top level heading could be "Add a notice" and then one section on "Degradation" and "Maintenance Window"? I don't know if that is confusing or too complicated.

This is an example of what the new Notice Modal will look like:

Image There is a new field called "Notice Type", where users will choose between "degradation" and "scheduled maintenance"

There is also a "Review Notice" feature so maybe that could be called out in this section, since you no longer go from the modal to "Publish Notice"

Image

| ---- | ---- |
| **Title** | Short, clear description of the incident <br>*Example: Increased error rates on US region* |
| **Status** | Current state of the incident: <br>- Investigating <br>- Identified <br>- Monitoring <br>- Resolved |
| **Message** *(optional)* | Additional details for your users <br>*Examples: known cause, expected resolution time* |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| **Message** | Additional details for your users <br>*Examples: known cause, expected resolution time* |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Messages are no longer optional

<!-- Image placeholder
{{< img src="#" alt="Status page showing a scheduled maintenance window for upcoming infrastructure work" style="width:100%;" >}}-->

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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Maintenance windows allow you to proactively communicate planned downtime or service impact before it happens. Unlike [degradations](#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.

Copy link
Contributor Author

@estherk15 estherk15 Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@reaganrazon Are all "notices" now referred to as degradations? Instead of #add-a-notice should it be #add-a-degredation?

1. Bars and Uptime Percentage
1. Bars Only
1. Component Name Only

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image This might not belong here, but it may be helpful to point out the hierarchy of component status. So if there are different notices that affect the same component, the worst severity takes precedent. Which is important with the introduction of maintenance windows because people might get confused.

Copy link

@reaganrazon reaganrazon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some comments/suggestions! Thank you!

@iadjivon iadjivon added the WORK IN PROGRESS No review needed, it's a wip ;) label Nov 14, 2025
Co-authored-by: Reagan Razon <115665609+reaganrazon@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

WORK IN PROGRESS No review needed, it's a wip ;)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants