You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org

Incident response/Lightweight report template: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Herron
mNo edit summary
imported>Krinkle
No edit summary
(3 intermediate revisions by 2 users not shown)
Line 17: Line 17:
}}
}}
<!-- Reminder: No private information on this page! -->
<!-- Reminder: No private information on this page! -->


<mark>Summary of what happened, in one or two paragraphs. Avoid assuming deep knowledge of the systems here, and try to differentiate between proximate causes and root causes.</mark>
<mark>Summary of what happened, in one or two paragraphs. Avoid assuming deep knowledge of the systems here, and try to differentiate between proximate causes and root causes.</mark>


'''Documentation''':
'''Documentation''':
* <mark>Todo (Link to relevant source code, graphs, or logs)</mark>
*
 
<mark>Link to relevant source code, graphs, or logs</mark>


==Actionables==
==Actionables==
* …
<mark>Create a list of action items that will help prevent this from happening again as much as possible. Link to or create a Phabricator task for every step.</mark>
<mark>Create a list of action items that will help prevent this from happening again as much as possible. Link to or create a Phabricator task for every step.</mark>


* <mark>To do #1 (TODO: Create task)</mark>
<mark>Add the [[phab:project/view/4758/|#Sustainability (Incident Followup)]] and the [[phab:project/profile/4626/|#SRE-OnFIRE (Pending Review & Scorecard)]] Phabricator tag to these tasks.</mark>
*<mark>To do #2 (TODO: Create task)</mark>
 
<mark>TODO: Add the [[phab:project/view/4758/|#Sustainability (Incident Followup)]] and the [[phab:project/profile/4626/|#SRE-OnFIRE (Pending Review & Scorecard)]] Phabricator tag to these tasks.</mark>


==Scorecard==
==Scorecard==
Line 37: Line 41:
!
!
!Question
!Question
!Score
!Answer
(yes/no)
!Notes
!Notes
|-
|-
! rowspan="5" |People
! rowspan="5" |People
|Were the people responding to this incident sufficiently different than the previous five incidents? (score 1 for yes, 0 for no)
|Were the people responding to this incident sufficiently different than the previous five incidents?
|
|
|
|
|-
|-
|Were the people who responded prepared enough to respond effectively (score 1 for yes, 0 for no)
|Were the people who responded prepared enough to respond effectively  
|
|
|
|
|-
|-
|Were more than 5 people paged? (score 0 for yes, 1 for no)
|Were fewer than five people paged?
|
|
|
|
|-
|-
| Were pages routed to the correct sub-team(s)? (score 1 for yes, 0 for no)
| Were pages routed to the correct sub-team(s)?  
|
|
|
|
|-
|-
|Were pages routed to online (business hours) engineers? (score 1 for yes,  0 if people were paged after business hours)
|Were pages routed to online (business hours) engineers? ''Answer “no” if engineers were paged after business hours.''
|
|
|
|
|-
|-
! rowspan="5" |Process
! rowspan="5" |Process
|Was the incident status section actively updated during the incident? (score 1 for yes, 0 for no)
|Was the incident status section actively updated during the incident?
|
|
|
|
|-
|-
|Was the public status page updated? (score 1 for yes, 0 for no)
|Was the public status page updated?
|
|
|
|
|-
|-
|Is there a phabricator task for the incident? (score 1 for yes, 0 for no)
|Is there a phabricator task for the incident?
|
|
|
|
|-
|-
|Are the documented action items assigned?  (score 1 for yes, 0 for no)
|Are the documented action items assigned?
|
|
|
|
|-
|-
|Is this a repeat of an earlier incident (score 0 for yes, 1 for no)
|Is this incident sufficiently different from earlier incidents so as not to be a repeat occurrence?
|
|
|
|
|-
|-
! rowspan="5" |Tooling
! rowspan="5" |Tooling
|Was there, before the incident occurred, open tasks that would prevent this incident / make mitigation easier if implemented? (score 0 for yes, 1 for no)
|To the best of your knowledge was the open task queue free of any tasks that would have prevented this incident? ''Answer “no” if there are''
''open tasks that would prevent this incident or make mitigation easier if implemented.''
|
|
|
|
|-
|-
|Were the people responding able to communicate effectively during the incident with the existing tooling? (score 1 for yes, 0 or no)
|Were the people responding able to communicate effectively during the incident with the existing tooling?
|
|
|
|
|-
|-
|Did existing monitoring notify the initial responders? (score 1 for yes, 0 for no)
|Did existing monitoring notify the initial responders?
|
|
|
|
|-
|-
|Were all engineering tools required available and in service? (score 1 for yes, 0 for no)
|Were the engineering tools that were to be used during the incident, available and in service?  
|
|
|
|
|-
|-
|Was there a runbook for all known issues present? (score 1 for yes, 0 for no)
|Were the steps taken to mitigate guided by an existing runbook?
|
|
|
|
|-
|-
! colspan="2" align="right" |Total score
! colspan="2" align="right" |Total score (count of all “yes” answers above)
|
|
|
|
|}
|}

Revision as of 21:14, 17 June 2022

document status: draft

Summary

Incident metadata (see Incident Scorecard)
Incident ID Lightweight report template Start YYYY-MM-DD hh:mm:ss
Task End YYYY-MM-DD hh:mm:ss
People paged Responder count
Coordinators Affected metrics/SLOs
Impact Who was affected and how? For user-facing outages: Estimate how many queries were lost, which regions were affected, or which types of clients (editors? readers? bots?), etc. Do not assume the reader knows what your service is or who uses it.

Summary of what happened, in one or two paragraphs. Avoid assuming deep knowledge of the systems here, and try to differentiate between proximate causes and root causes.

Documentation:

Link to relevant source code, graphs, or logs

Actionables

Create a list of action items that will help prevent this from happening again as much as possible. Link to or create a Phabricator task for every step.

Add the #Sustainability (Incident Followup) and the #SRE-OnFIRE (Pending Review & Scorecard) Phabricator tag to these tasks.

Scorecard

Incident Engagement™ ScoreCard
Question Answer

(yes/no)

Notes
People Were the people responding to this incident sufficiently different than the previous five incidents?
Were the people who responded prepared enough to respond effectively
Were fewer than five people paged?
Were pages routed to the correct sub-team(s)?
Were pages routed to online (business hours) engineers? Answer “no” if engineers were paged after business hours.
Process Was the incident status section actively updated during the incident?
Was the public status page updated?
Is there a phabricator task for the incident?
Are the documented action items assigned?
Is this incident sufficiently different from earlier incidents so as not to be a repeat occurrence?
Tooling To the best of your knowledge was the open task queue free of any tasks that would have prevented this incident? Answer “no” if there are

open tasks that would prevent this incident or make mitigation easier if implemented.

Were the people responding able to communicate effectively during the incident with the existing tooling?
Did existing monitoring notify the initial responders?
Were the engineering tools that were to be used during the incident, available and in service?
Were the steps taken to mitigate guided by an existing runbook?
Total score (count of all “yes” answers above)