WIP: Distill incident-handling procedures into single playbook

nb110240 · Nov 9, 2021 · f0c9027 · f0c9027
1 parent 7b82b09
commit f0c9027
Show file tree

Hide file tree

Showing 14 changed files with 460 additions and 2 deletions.
diff --git a/playbooks/README.md b/playbooks/README.md
@@ -31,6 +31,7 @@ practice should be incorporated, submit a PR!
 | [Extracting Services](/playbooks/extracting-services.md#readme) | When and why to consider extracting or decoupling systems |
 | [GraphQL Schema Design](/playbooks/graphql-schema-design.md#readme) | What are our best practices for GraphQL Schema Design? |
 | [Hokusai](/playbooks/hokusai.md#readme) | a CLI to manage applications deployed to Kubernetes |
+| [Incident Handling](/playbooks/incident-handling.md#readme) | How engineers share on-call duties and provide urgent support |
 | [How to give a good Informational](/playbooks/informationals.md#readme) | What are the steps needed to give someone a great experience. |
 | [Jira](/playbooks/jira.md#readme) | Working with Jira boards and tickets |
 | [Kubernetes](/playbooks/kubernetes.md#readme) | Deploying containerized applications at Artsy |

diff --git a/playbooks/images/on-call-slo.jpg b/playbooks/images/on-call-slo.jpg
diff --git a/playbooks/images/opsgenie-addengs-2.png b/playbooks/images/opsgenie-addengs-2.png
diff --git a/playbooks/images/opsgenie-addengs-3.png b/playbooks/images/opsgenie-addengs-3.png
diff --git a/playbooks/images/opsgenie-addengs-4.gif b/playbooks/images/opsgenie-addengs-4.gif
diff --git a/playbooks/images/opsgenie-override-0.png b/playbooks/images/opsgenie-override-0.png
diff --git a/playbooks/images/opsgenie-override-1.png b/playbooks/images/opsgenie-override-1.png
diff --git a/playbooks/images/opsgenie-override-2.png b/playbooks/images/opsgenie-override-2.png
diff --git a/playbooks/images/opsgenie-responding-0.png b/playbooks/images/opsgenie-responding-0.png
diff --git a/playbooks/images/opsgenie-schedule-0.png b/playbooks/images/opsgenie-schedule-0.png
diff --git a/playbooks/images/opsgenie-schedule-1.png b/playbooks/images/opsgenie-schedule-1.png
diff --git a/playbooks/images/opsgenie-schedule-2.png b/playbooks/images/opsgenie-schedule-2.png
diff --git a/playbooks/incident-handling.md b/playbooks/incident-handling.md
diff --git a/playbooks/support/README.md b/playbooks/support/README.md
@@ -3,7 +3,6 @@
 <!-- START doctoc generated TOC please keep comment here to allow auto update -->
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 
-
 - [Wait!](#wait)
 - [Process Overview](#process-overview)
 - [On-Call Responsibilities](#on-call-responsibilities)
@@ -108,7 +107,7 @@ See the [responding doc](responding.md#severity-of-incidents) for levels of seve
 
 - On the last day of your shift verify in [OpsGenie schedule](https://artsy.app.opsgenie.com/schedule/whoIsOnCall)
   who is coming to replace you and have a quick check in with them about current outstanding issues.
-- Update header of the slack #incidents channel with the current on-call engeneers' names.
+- Update header of the slack #incidents channel with the current on-call engineers' names.
 
 ## Helpful Resources and Playbooks