> 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/july-2026.md).

# July 2026

### New features and improvements

* 🎉 We launched **Service topology** (closed beta) — a live, connected view of your services and the dependencies between them. Instead of maintaining a static architecture diagram, ilert reconstructs the dependency graph automatically and gives you an interactive **Service Health map** to explore blast radius and likely root cause during an incident. The topology also gives **AI SRE** richer context for alert triage and root cause analysis
* Powering the topology, we introduced **telemetry sources** (closed beta) — OpenTelemetry (OTLP) ingestion endpoints your OTel collectors or services push traces to. ilert derives the service-to-service dependencies from those traces, auto-creates unknown services in your service catalog and keeps the graph up to date. We are planning on opening more interface here soon.
* We introduced **labels for services**, our first step towards labels on all team owned entities
* We significantly expanded the internal ilert MCP server behind **AI SRE**, giving your agents far richer access to ilert — most notably around the new incident management
* We added **conference bridges to incidents**, including automatic provisioning of e.g. a **Microsoft Teams meeting** with the acting user as organizer, so responders can jump straight into a call from the incident
* We added "Compass" **incident guides** to keep track of the steps your team should follow during a major incident
* You can now **link root cause investigations to incidents**, connecting your RCA work directly to the incident it belongs to
* **Postmortems** can now act as standalone entities and received a brand-new live editor + browse list view
* We added an **hourly rotation length** to recurring on-call schedules, next to the existing daily and weekly rotations, and made the preview timeline noticeably faster for dense schedules
* We extended the **alert list and alert count API** with filters for services and severities
* We heard you and disabled user mentions by default on alert message updates in Slack ChatOps notifications, we still annotate if the message is sent in a channel created by the bot
* Call flows: the **AI voice agent node** is now available for EU customers, the **IVR menu node** can disable voice detection, and route-call agents are now greeted in their own locale

### Integration updates

* We have introduced new inbound integrations: **OpenObserve**, **OpenSearch Dashboards**, **openITCOCKPIT**, **OpenNMS** and **Odoo**
* The **SignalFx** integration has been rebranded to **Splunk Observability Cloud**
* The **Zammad** converter now supports more ticket states


---

# 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/july-2026.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.