> For the complete documentation index, see [llms.txt](https://docs.blocktorch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blocktorch.xyz/use-cases/managing-incidents/post-mortem.md).

# Post mortem

Writing a post-mortem is an essential process that follows the occurrence of a significant incident within a project or operation. It serves as a reflective analysis, aimed at understanding what went wrong, what was successful, and how similar incidents can be prevented or handled better in the future.&#x20;

Integrating data insights from **blocktorch** into a post-mortem can enhance the depth of the report. For instance, [monitoring](/use-cases/monitoring.md) data and visuals can pinpoint when and where the issue originated and metrics on performance degradation can illustrate the incident's impact. [Logs](/use-cases/searching/logs.md) and [traces](/use-cases/tracing.md) can support comprehension. By embedding such data, stakeholders can make informed decisions on corrective actions and strategic improvements, ensuring a comprehensive and insightful post-mortem.

{% hint style="info" %}
If you are interested in being a testing partner for us for a POC of automated post mortem generation through AI, please [let us know](mailto:contact@blocktorch.xyz).
{% endhint %}
