> 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/changelog/2024/april-2024.md). # April 2024 ### New features and improvements * We have reworked the setup flow for Alert actions and Connectors, admins will now find a hugely **improved Connector UX** * We have launched **incident timelines** that give fine grained audit insights into what has changed by whom on an incident during its lifecycle * We have launched **call logs for call flows** (call routing 2.0) providing fine grained audit insights into what has happend during and outside of the call * The incident list will now live update, similar to the alert list * We have added a new inbound integration: Victoria Metrics * We have added a new inbound integration: Honeycomb * We have improved the inbound Email integration, now providing custom alert templates e.g. to include the sender in the alert summary --- # 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/changelog/2024/april-2024.md?ask=&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.