Currently, MongoDB Atlas send email alerts about the timing of Atlas cluster maintenance, but these notifications often lack a clear summary of what actions are being taken.
To be fair, many large organizations require a certain level of visibility and control. Even though we emphasize that MongoDB has many built-in capabilities to ensure maintenance causes minimal disruption, customer teams still need to review their application logs. When they encounter exceptions in those logs, it causes concern—especially if the application surfaces the error to their end-users or customers.
Therefore, I believe it would be helpful to include more context in the maintenance notification emails, including any action that they need to do (if any). This would enable customers to better communicate the details internally to their relevant teams.
Currently, MongoDB Atlas send email alerts about the timing of Atlas cluster maintenance, but these notifications often lack a clear summary of what actions are being taken.
To be fair, many large organizations require a certain level of visibility and control. Even though we emphasize that MongoDB has many built-in capabilities to ensure maintenance causes minimal disruption, customer teams still need to review their application logs. When they encounter exceptions in those logs, it causes concern—especially if the application surfaces the error to their end-users or customers.
Therefore, I believe it would be helpful to include more context in the maintenance notification emails, including any action that they need to do (if any). This would enable customers to better communicate the details internally to their relevant teams.