Postmortem
A written report produced after an incident is resolved, recording the incident timeline, scope of impact, root cause, and improvement items. It promotes a blameless postmortem culture and is an important artifact in SRE practice.
Timeline (last 90 days)
Postmortem (post-incident review document) follows the principle of "blameless postmortem" in SRE culture, focusing on system and process defects rather than assigning personal responsibility.
A postmortem is the standard process for large tech companies to handle incidents, typically including a timeline, root cause analysis, quantification of the impact scope, and action items to prevent recurrence.
A postmortem is a retrospective document written after failure recovery, usually including the failure timeline, scope of impact, root cause analysis, handling process and improvement items to prevent recurrence, emphasizing "focus on the issue, not the person".
The Postmortem culture in the Google SRE framework requires that every post-incident action item have one and only one named owner and a deadline, rather than being broadly attributed to a team.
In SRE practice, public postmortems with a blameless culture are regarded as one of the core means of improving system reliability.
Post-incident review reports typically include a fault timeline, the scope of affected services, root cause analysis, and subsequent improvement measures.
The value of technical documentation, design reviews (RFCs/Design Docs), and incident post-mortems lies not only in their conclusions but also in the reasoning process itself.
All Facts (7)
Postmortem (post-incident review document) follows the principle of "blameless postmortem" in SRE culture, focusing on system and process defects rather than assigning personal responsibility.
50%UnverifiedA postmortem is the standard process for large tech companies to handle incidents, typically including a timeline, root cause analysis, quantification of the impact scope, and action items to prevent recurrence.
50%UnverifiedA postmortem is a retrospective document written after failure recovery, usually including the failure timeline, scope of impact, root cause analysis, handling process and improvement items to prevent recurrence, emphasizing "focus on the issue, not the person".
50%UnverifiedThe Postmortem culture in the Google SRE framework requires that every post-incident action item have one and only one named owner and a deadline, rather than being broadly attributed to a team.
50%UnverifiedIn SRE practice, public postmortems with a blameless culture are regarded as one of the core means of improving system reliability.
50%UnverifiedPost-incident review reports typically include a fault timeline, the scope of affected services, root cause analysis, and subsequent improvement measures.
50%UnverifiedThe value of technical documentation, design reviews (RFCs/Design Docs), and incident post-mortems lies not only in their conclusions but also in the reasoning process itself.
50%