What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

Urgent cluster maintenance notifications that fall outside the regular maintenance window are currently delivered only via email. Email is fragile for time-sensitive operational notifications: it can be missed outside business hours, filtered by mail rules, or delayed.

We recently received an email notifying us of an urgent cluster patch scheduled outside our regular maintenance window. Because the email arrived late around noon, we noticed it only by chance and were able to complete the maintenance before the deadline. On a previous occasion, however, we did not detect a similar urgent maintenance notification until shortly before the deadline, and our service experienced impact from the resulting failover.

We have confirmed with customer support that there is currently no supported way to receive these urgent maintenance notifications through channels other than email.

What would you like to see happen?

Describe the desired outcome or enhancement.

We would like urgent maintenance notifications to be deliverable through additional channels beyond email — for example, Slack, webhooks, SMS, or PagerDuty. Ideally, the existing Alerts / Integrations framework in Atlas would be extended so that maintenance notifications can be routed through the same channels already used for operational alerts.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

Missing an urgent maintenance notification has a direct business impact: failovers triggered by patches we were not prepared for can cause service degradation visible to our end users. Delivering the same notification through an on-call-friendly channel would significantly reduce the risk of missed maintenance windows and the resulting customer-facing impact.

This is particularly important for teams operating outside the US Eastern time zone, where urgent notifications scheduled in ET often arrive late at night local time, making email-only delivery especially unreliable.

What steps, if any, are you taking today to manage this problem?

Today we rely entirely on email monitoring, supplemented by ad-hoc manual checks of the Atlas console. We have considered setting up mail-filter-based forwarding to Slack or our paging system, but this approach is brittle (depends on subject-line patterns that may change), adds an unsupported component to a critical alerting path, and does not provide acknowledgement or escalation semantics that a proper integration would.