Notifications
Use this guide to explore options for keeping stakeholders informed before, during, and after patch cycles.
Who Should Be Notified
Before patching, consider notifying:
- Application and service owners whose systems are being patched.
- On‑call engineers and SRE or operations teams.
- Security and compliance stakeholders for major releases.
- Change approvers and Change Advisory Board (CAB) members.
Types of Notifications
Common notification points include:
| Patching stage | Description | Notification channel |
|---|---|---|
| Pre-maintenance | Upcoming patch windows, scope, and potential impact. | Email report |
| Start | Confirmation that a patch job has started. | Reminder 2 days before / night of |
| Progress | Summary of successes/failures so far, especially for long-running jobs. | None |
| Completion | Final status, including any hosts that require follow-up. | Patching summary report |
| Emergency releases | Special notice with clearer escalation paths. | None |
Patching Summary Report
Upon completion of patching, Cloudaware generates a summary report with the results. The report can be delivered via email, chat tools such as Slack or Microsoft Teams, or integrated ticket updates in your ITSM platform.