-
Notifications
You must be signed in to change notification settings - Fork 2
/
incident_resolution_template_playbook.json
89 lines (89 loc) · 4.66 KB
/
incident_resolution_template_playbook.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
{
"channel_name_template": "Incident: \u003cname\u003e",
"checklists": [
{
"items": [
{
"title": "Add on-call engineer to channel"
},
{
"command": "/zoom start",
"title": "Start bridge call"
},
{
"title": "Update description with current situation"
},
{
"command": "/jira create",
"title": "Create an incident ticket"
},
{
"title": "Assign severity in description (ie. #sev-2)"
},
{
"title": "(If #sev-1) Notify @vip"
}
],
"title": "Setup for triage"
},
{
"items": [
{
"title": "Add suspected causes here and check off if eliminated"
}
],
"title": "Investigate cause"
},
{
"items": [
{
"title": "Confirm issue has been resolved"
},
{
"title": "Notify customer success managers"
},
{
"title": "(If sev-1) Notify leader team"
}
],
"title": "Resolution"
},
{
"items": [
{
"title": "Send out survey to participants"
},
{
"title": "Schedule post-mortem meeting"
},
{
"title": "Save key messages as timeline entries"
},
{
"title": "Publish retrospective report"
}
],
"title": "Retrospective"
}
],
"description": "Customize this playbook to reflect your own incident resolution process.",
"message_on_join": "Hello and welcome!\n\nThis channel was created as part of the **Incident Resolution** playbook and is where conversations related to this release are held. You can customize this message using markdown so that every new channel member can be welcomed with helpful context and resources.",
"message_on_join_enabled": true,
"metrics": [],
"reminder_timer_default_seconds": 86400,
"retrospective_enabled": true,
"retrospective_reminder_interval_seconds": 86400,
"retrospective_template": "### Summary\nThis should contain 2-3 sentences that give a reader an overview of what happened, what was the cause, and what was done. The briefer the better as this is what future teams will look at first for reference.\n\n### What was the impact?\nThis section describes the impact of this playbook run as experienced by internal and external customers as well as stakeholders.\n\n### What were the contributing factors?\nThis playbook may be a reactive protocol to a situation that is otherwise undesirable. If that's the case, this section explains the reasons that caused the situation in the first place. There may be multiple root causes - this helps stakeholders understand why.\n\n### What was done?\nThis section tells the story of how the team collaborated throughout the event to achieve the outcome. This will help future teams learn from this experience on what they could try.\n\n### What did we learn?\nThis section should include perspective from everyone that was involved to celebrate the victories and identify areas for improvement. For example: What went well? What didn't go well? What should be done differently next time?\n\n### Follow-up tasks\nThis section lists the action items to turn learnings into changes that help the team become more proficient with iterations. It could include tweaking the playbook, publishing the retrospective, or other improvements. The best follow-ups will have a clear owner assigned as well as due date.\n\n### Timeline highlights\nThis section is a curated log that details the most important moments. It can contain key communications, screen shots, or other artifacts. Use the built-in timeline feature to help you retrace and replay the sequence of events.",
"run_summary_template": "**Summary**\n\n**Customer impact**\n\n**About**\n- Severity: #sev-1/2/3\n- Responders:\n- ETA to resolution:",
"run_summary_template_enabled": true,
"signal_any_keywords": [
"sev-2",
"#incident",
"this is serious",
"sev-1"
],
"signal_any_keywords_enabled": true,
"status_update_enabled": true,
"title": "Incident Resolution Template",
"version": 1
}