> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/getting-started/release-notes/25.9-september-2025.md).

# 25.9 - September 2025

Release Notes 25.9 for September 2025

### Summary

In **25.9** AppVis is now available in Insight UI

### AppVis now available in Insight UI&#x20;

<figure><picture><source srcset="https://25768351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68Wb63XzG9guH74bkPEb%2Fuploads%2FYEBIm6vvZto6OfzZE63e%2FAppVis-Dark.png?alt=media&amp;token=e8161c0c-afa0-4d36-8f9b-088c46758ab6" media="(prefers-color-scheme: dark)"><img src="https://25768351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68Wb63XzG9guH74bkPEb%2Fuploads%2F4FFZmsEW17pytAuaYcPB%2FAppVis-Light.png?alt=media&amp;token=ae28f0ba-fbc0-4b1e-8250-3d8d3e4a03cb" alt="AppVis in Insight UI"></picture><figcaption></figcaption></figure>

Our AppVis page is now available in Insight UI light and dark modes.  With AppVis you can quickly identify the applications running on your network with recognised logos for each one.&#x20;

Find out more about [AppVis](https://help.highlight.net/status/appvis/appvis.md) and [Insight UI](https://help.highlight.net/getting-started/useful-information/insight-ui.md).&#x20;

### Cisco Meraki - cameras and sensors now available in Reporting - Beta <a href="#cisco-meraki-cameras-and-sensors-now-supported-beta" id="cisco-meraki-cameras-and-sensors-now-supported-beta"></a>

You can autodiscover IoT items along with the rest of your estate and receive notification if these are down or in an alerting state.  It's also now possible to include these in reports for a day, week or month to review availability and health over time. &#x20;

### Bug fixes

* **Audit Log:**  Resolved a problem with changes to large containers not being audited. &#x20;

### Service description

The [Highlight Service Description document](https://help.highlight.net/getting-started/new-user/service-description.md) concisely describes how Highlight works and its key features. It was last updated for 25.6 and is available on the Help & Support Centre.

### Browser compatibility

All Highlight releases are tested on the current version of:

* ![Chrome](https://support.highlight.net/help/images/browser_chrome.png)

  #### Chrome
* ![Edge](https://support.highlight.net/help/images/browser_edge.png)

  #### Edge
* ![Firefox](https://support.highlight.net/help/images/browser_ff.png)

  #### Firefox

Find out more about [Highlight supported browsers](https://help.highlight.net/getting-started/useful-information/browsers-supported.md).

### Get in touch

More details on all of Highlight’s features are available on the Help & Support Centre or [contact us](https://help.highlight.net/getting-started/contact-us.md) for assistance.


---

# 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://help.highlight.net/getting-started/release-notes/25.9-september-2025.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.
