> 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/2025/may-2025-5.md).

# July 2025

### New features and improvements

* **Alerts** and the event API now support **labels** (key value string maps)
* **Alerts** and the event API now support **logs** (new eventType LOG and logs array field)
* Alerts now support action items
* The **event explorer** now lets you discover any **correlated alert actions** that were triggered through the updates of an event to an alert
* We have migrated most billing and subscriptions pages to our new front-end stack
* While the **ilert Responder AI Agent** is still in closed BETA, we have completely overhauled the agent experienced and the real-time collaboration with the agents in the chat UI

### Integration updates

* New inbound integration **Fleet**
* New inbound integration **ConnectWise PSA**
* New inbound integration **DeadMansSnitch**
* New inbound integration **FortiSOAR**


---

# 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/2025/may-2025-5.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.