> 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/january-2025.md). # January 2025 ### New features and improvements * New **heartbeat** experience is in closed **BETA**, supporting millions of heartbeats with sub minute ping intervals and additional features like assigning multiple heartbeats to the same alert source for individual grouping mechanics * We have launched our **new alert reports in GA**, it is the first report that gets updated, stay tuned as we overhaul the rest of the reports with a completely new UI stack and additional features in the next weeks * We have released a new iteration of **Audience Specific Status Pages**, enhancing many of its features (such as branding or notification content filters) and making it even easier to setup complex pages * We added a new **detailed** information widget to incident coms **publish info**, showing exactly which resources and susbcribers are notified ### Integration updates * **Site24x7** inbound integration * Autotask outbound supports custom body fields now * SNS inbound integration has been enhanced to support a new \_ilert.parsedMessage field, which can be used to access the keys of JSON messages in ilert templating configurations * Cisco Meraki now supports auto resolving of alerts --- # 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/january-2025.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.