> 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/september-2024.md).
# September 2024
### New features and improvements
* **ilert search** is now out of closed beta and available to all ilert users
* The i**lert dashboard** is now available to all ilert users in its **editable** mode, you can now create, customize and share your own dashboards with specific users or the whole account
* We have introduced a new feature to the **alert resolve bulk** action that automatically **suggest similar open alerts** based on ilert AI
* Alert detail markdown rendering has been adjusted to require explict header syntax `#` instead other inline versions e.g. `--` which caused confusion
### Integration updates
* Github action check runs have been fixed to include the Failure subtype
* We have added the [Ansible AWX ](/integrations/inbound-integrations/awx.md)inbound integration
---
# 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/september-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.
.gif?alt=media&token=0eb36661-f715-421d-907c-2bc92b0a98fc)