> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/knowledge-base/reporting-and-analytics/can-i-create-knowledge-base-articles-from-incidents.md).

# Can I create knowledge base articles from incidents?

Yes! ilert automatically generates post-mortem documents from incidents that can be used to create knowledge base articles.

## Automatic post-mortem generation

ilert automatically creates comprehensive post-mortem documents in Markdown format for each incident. These documents include:

* **Incident timeline**: Detailed chronology of events
* **Root cause analysis**: AI-generated insights into what caused the incident
* **Resolution steps**: Actions taken to resolve the issue
* **Lessons learned**: Key takeaways and recommendations
* **Prevention measures**: Suggestions to prevent similar incidents

## Export options

While ilert doesn't currently support direct publishing to external knowledge bases like Confluence or ticketing systems like Ivanti, you can easily export the generated post-mortem documents:

* **Copy and paste**: Copy the Markdown content directly into your knowledge base
* **Manual export**: Download the post-mortem document and upload it to your preferred system
* **API integration**: Use ilert's REST API to programmatically retrieve post-mortem content

## Integration possibilities

You can integrate the post-mortem content with your existing systems by:

* **Confluence**: Copy the Markdown content into Confluence pages
* **Ivanti tickets**: Paste the incident summary into ticket descriptions
* **Custom knowledge bases**: Import the structured data into your internal documentation system

## Getting started

To access post-mortem documents for your incidents, navigate to the incident details page in ilert. The post-mortem will be available once the incident is resolved.

{% hint style="info" %}
**Related Documentation**

* [Incidents](/incidents-and-status-pages/incidents.md)
* [AI-Generated Postmortems](https://app.gitbook.com/s/-M76ygPnS4HUcFSX8ulm/incidents-and-status-pages/incidents/postmortems)
* [REST API Reference](/developer-docs/rest-api/api-reference.md)
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/knowledge-base/reporting-and-analytics/can-i-create-knowledge-base-articles-from-incidents.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.