Last active
May 5, 2016 16:22
-
-
Save flomotlik/333ce689db7099911f9e to your computer and use it in GitHub Desktop.
Codeship Debrief Template
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Service Interruption Debrief | |
| ## Brief Executive Summary | |
| EXECUTIVE SUMMARY HERE | |
| ***On Call during outage***: | |
| ***Time outage started***: | |
| ***Time it was discovered***: | |
| ***Time it was resolved***: | |
| ***Time of writing debrief***: | |
| ##Affected Services | |
| * ... | |
| ## Technical Issue | |
| ### Detailed description of the issue | |
| DETAILED DESCRIPTION OF ISSUE HERE | |
| ### Discovering the Issue | |
| DESCRIPTION OF HOW IT WAS DISCOVERED BY WHOM AND WHEN | |
| #### Pagerduty Alerts fired | |
| * ... | |
| #### Issues with how on-call team handled outage? | |
| * ... | |
| #### Future improvements for on-call team | |
| * ... | |
| ### Resolving the Issue | |
| ***In Charge***: | |
| ####Steps taken including timestamps | |
| * ... | |
| ### How can we improve our issue resolve efforts in the future | |
| DESCRIBE WHAT IS A BETTER WAY TO IMPROVE THIS EFFORT IN THE FUTURE | |
| * ... | |
| #### Missing Alerts | |
| * ... | |
| #### Missing Metrics/Logs | |
| * ... | |
| ### Tasks to resolve the technical issue | |
| * ... | |
| ## Customer Communication | |
| ***Who took over customer communication***: | |
| ###Steps taken to inform customers with timestamp: | |
| * ... | |
| * ... | |
| ### How can we improve our customer communication in the future | |
| DESCRIBE STEPS TO IMPROVE CUSTOMER COMMUNICATION IN THE FUTURE |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment