> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/changelog/june-2024/2024-06-26-release.md).

# 2024-06-26-Release

Version 1.61.1 • JUN 26, 2024

## New Features

* [NATS Event Bus](#nats-event-bus)
* [Filter By Regex processor](https://github.com/observIQ/bindplane-docs/blob/main/integrations/processors/filter-by-regex.md), available for Google licenses
* Agent's page is now sortable by labels
* [SQL Query Source](https://github.com/observIQ/bindplane-docs/blob/main/integrations/sources/sql-query.md)

## Bug Fixes

* Add validation to guard against applying resources without `metadata.name`
* Correctly handle deleting multiple configs
* Handle duplicating configs without a current version

## Other

* Rebrand Google Chronicle to Google SecOps

### NATS Event Bus

Enterprise users operating BindPlane in [High Availability](https://github.com/observIQ/bindplane-docs/blob/main/production-checklist/bindplane/high-availability/README.md) can now use the [NATS Event Bus](https://github.com/observIQ/bindplane-docs/blob/main/configuration/bindplane/nats-as-event-bus.md). The NATS Event Bus eliminates the need for an external event bus such as Google Pub/Sub or Apache Kafka.


---

# 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.bindplane.com/changelog/june-2024/2024-06-26-release.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.