> 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/2026/may-2026.md). # May 2026 ### New features and improvements * 🎉 Our brand new **Incident management** is now **generally available**! Built on a new parallel paging architecture with a standalone incident responder and dedicated streams, it brings real-time, collaborative major-incident handling with **private subscribers**, an **incident timeline**, subscriber sync and real-time websocket updates. It also cleanly **separates incidents from status updates**, giving you dedicated handling for each. {% hint style="info" %} **Existing customers** created before 19.05.2026 have not yet been automatically switched to the new Incident management features. We will be rolling these out over the next weeks, making sure everyone has a smooth transition. {% endhint %} * We introduced **multiple service aliases**, allowing you to map several aliases to a single service * We introduced **edge connections for ilagent**, enabling new `edge_connect` alert actions for connectivity at the edge (this helps new customers replace OEC) * We added **severity and services templating in alert sources**, giving you more control over how inbound payloads map to ilert severity and services * Service templates support an auto-creation mode, letting you automatically create unregistered services from incoming event payloads ### Integration updates * We have introduced a new **Dynatrace Workflows** outbound integration * The **WhaTap** integration now extracts link fields * We added more **Auvik** regions ### Marketplace * We launched new **marketplace apps** — be sure to try them out (Profile Menu -> Marketplace -> Visit Apps): * **On-Call Health** — analyze on-call schedules to surface health metrics, risk factors and trends across your teams. Spot burnout early and make data-driven scheduling decisions to improve on-call quality * **Notification Preference Policy** — audit notification preference compliance across your team. Define policies for required channels and delays, then highlight users whose preferences don't meet your coverage requirements --- # 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/2026/may-2026.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.