# May 2024

### New features and improvements

* We have introduced [event filters](/alerting/configure-alerting/alert-sources.md#event-filter) for alert source, you can now add custom conditions to create or drop alerts
* We have introduced the [ICL ilert conditional language](broken://spaces/-M76ygPnS4HUcFSX8ulm/pages/l0DnG2KVyQN3jcBKbyXf)
* We have introduced a new ilert AI feature [event content similarity grouping for alert sources](/alerting/configure-alerting/alert-sources/using-ilert-ai-for-alert-grouping.md)
* Private status pages now support a new authorization procedure, through magic link emails, you can define one or multiple domains (or specific emails) to allow users outside of your ilert organization to access the private status page (look for **email based login** in the Authorization tab)
* We have reworked the Jira outbound integration
* The Stackdriver/GCP inbound integration now supports the Error reporting payload
* The MongoDB inbound integration has been updated to support new event types
* We have introduce a new [inbound integration 4me](/integrations/inbound-integrations/4me.md)
* We have improved the alert source throttling API warning display and added it to the alert source list


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ilert.com/changelog/2024/may-2024.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
