# hachyderm postmortem: _[title]_

_please do not change the format or delete sections_
_fill out anything in []_

| <!-- --> | <!-- --> |
|---------------|----------------------|
| Author | _[author]_ |
| Collaborators | _[collaborators]_ |
| Status | _[draft, published]_ |

## executive summary

| <!-- --> | <!-- --> |
|------------|----------------|
| Impact | _[impact]_ |
| Root Cause | _[root cause]_ |

## problem summary

| <!-- --> | <!-- --> |
|---------------------|-----------------|
| Duration of problem | _[duration]_ |
| User impact | _[user impact]_ |
| Detection | _[detection]_ |
| Resolution | _[resolution]_ |

## background

<!-- what does a reader need to know to understand the rest of the doc -->

## root causes and trigger

<!-- the root cause is what is at the heart of what happened. root cause
analysis is the most important part of the post-mortem. -->
<!-- the trigger is what caused the issue to occur. this may not be the
same as the root cause -->

## Impact

<!-- what was the impact of the issue in terms of user experience or
necessary changes to infrastructure -->

## Lessons Learned

<!-- what have we learned that we can take away from this incident? -->

## Things that went well

<!-- celebrate the good things in life -->

## Things that went poorly

<!-- what would we have prefered had not happened during the response? -->

## Where we got lucky

<!-- we all get a little lucky sometimes -->

## Action items

<!-- what could or did we change to either prevent this issue from
happening again, detect it sooner, or mitigate the issue? -->

<!-- "type" is one of "repair", "prevent", or "detect". -->

| Action item | Type | GitHub Issue |
|-------------|--------------|--------------|
| _[ ]_ | _[ ]_ | _[ ]_ |
| _[ ]_ | _[ ]_ | _[ ]_ |