Knowledgebase

Automating Notifications and Reporting Print

  • devopsinfrastructure, devops, backup, guide, howto, solution, zillionkinghost, hosting
  • 0

Keeping people informed.

WHAT TO AUTOMATE

Deployment notifications Incident alerts Backup and task status Periodic operational summaries

WHAT A DEPLOYMENT NOTIFICATION SHOULD SAY

What was deployed, by whom, to where, and whether it succeeded.

WHY

So everyone knows what changed, which is the first question in any incident.

WHAT A WEEKLY SUMMARY MIGHT INCLUDE

Deployments made Incidents and their duration Resource trends Alerts that fired Anything approaching a limit

WHERE TO SEND THESE

Somewhere the team actually reads.

WHAT TO AVOID

Volume that trains people to ignore Notifications requiring no action and conveying no information

WHAT TO DISTINGUISH

Alerts requiring action now Information worth knowing

WHAT TO ROUTE DIFFERENTLY

Those two, to different places.

WHAT TO REVIEW

Whether anyone reads what you send.

If not, stop sending it or change what it contains.

WHAT TO KEEP

A record, regardless of whether a notification was read.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot