In this onboarding tutorial, we'll go over how to easily build a retrospective within FireHydrant.
A retrospective (postmortem) is invaluable for learning from incidents and turning real issues into scalable solutions. With the help of FireHydrant, you'll be able to streamline your retrospective process, saving your team valuable time and resources while also ensuring your systems are resilient for the future.
Once an incident is resolved, you'll have the option to create a templated retrospective (or retro) for the given incident within the FH UI by clicking "Create retrospective for incident".
Along with FireHydrant automatically filling in information that was collected during the incident, you'll still have the option to edit the following key aspects:
- Timeline Highlights: Events and/or chatter collected from both Slack and FH's UI that were deemed important during an incident.
- Milestones: The time(s) at which key moments occurred (started, acknowledged, resolved, etc.).
- Deploy Events: Change events marked as suspicious or as a culprit(s).
- Contributing Factors: 5 Whys / RCA.
- Lessons Learned: Open-ended team storytelling on how to improve for the future.
- Follow-Ups: Outstanding follow-ups (after an incident was mitigated but not fully resolved).
Once you're finished editing your retrospective, you'll be able to publish your retrospective by clicking "Publish". From here, FireHydrant will automatically generate a PDF which can be viewed/downloaded by click "View PDF".
This PDF will include a plethora of items such as:
- Incident Severity
- Impacted Inventory (functionalities, services, and environments)
- Lessons Learned
- Contributing Factors
- Timeline Highlights
Again, this will allow you to streamline your retrospective process, saving you time and resources when it comes to fully resolving issues and keeping your systems resilient. Next, we'll discuss how we can automate our incident response process to give our teams the ease of mind during an incident.