> 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/january-2025/2025-01-22-release.md).

# Jan 22, 2025 - v1.85.0

Self-hosted

## Bug Fixes

* Resolved an issue where rollouts could become "stuck" if an event was dropped due to a network issue

## New Features

* New Processors
  * [Unroll](https://github.com/observIQ/bindplane-docs/blob/main/integrations/processors/unroll.md)
  * [Split](https://github.com/observIQ/bindplane-docs/blob/main/integrations/processors/split.md)
* [OpenShift Gateway Agent](https://github.com/observIQ/bindplane-docs/blob/main/deployment/kubernetes/collector/install.md)
* [Web URL configuration option](https://github.com/observIQ/bindplane-docs/blob/main/configuration/bindplane/README.md#web-url)
* [Postgres Max Connection Lifetime configuration option](https://github.com/observIQ/bindplane-docs/blob/main/configuration/bindplane/README.md#postgres)
* [Splunk Search API source](https://github.com/observIQ/bindplane-docs/blob/main/integrations/sources/splunk-search-api.md)
* [Bolt Store to Postgres migration command](#bolt-store-to-postgres)

### Bolt Store to Postgres

Migrating from Bolt Store to Postgres is supported with `system` authentication.

```bash
sudo BINDPLANE_CONFIG_HOME=/var/lib/bindplane \
  /usr/local/bin/bindplane migrate-store <new database name> \
  --config /etc/bindplane/config.yaml
```

### New Beta Features

Beta features are subject to change and can contain bugs. Please use beta features with caution against non critical workloads.

#### Configuration V2 and Advanced Routing

Bindplane v1.85.0 introduces the new configuration topology with advanced routing capabilities.

Previously, users required the [Filter by Condition](https://github.com/observIQ/bindplane-docs/blob/main/integrations/processors/filter-by-condition.md) processor for handling routing between sources and destinations. Now, users can connect sources and destinations explicitly, and avoid duplicating data across multiple destinations.

Existing configurations can be upgraded to to the new v2 topology by using the advanced "Upgrade to v2 beta" option.

{% hint style="info" %}
**NOTE**

It is recommended to duplicate your configuration before proceeding, and test the new functionality against the duplicate configuration.
{% endhint %}

<figure><img src="https://github.com/observIQ/bindplane-docs/blob/main/.gitbook/assets/release-notes-bindplane-2025-01-22-release-image-1.png" alt="Bindplane docs - 2025-01-22-Release - image 1"><figcaption></figcaption></figure>

Once upgraded, you will need to configure routing from source to destination.

<figure><img src="https://github.com/observIQ/bindplane-docs/blob/main/.gitbook/assets/release-notes-bindplane-2025-01-22-release-image-2.png" alt="Bindplane docs - 2025-01-22-Release - image 2"><figcaption></figcaption></figure>

This example shows the routing connector being used to route Prometheus source to Google Managed Prometheus, Kubelet to Google Cloud, and both sources to a Prometheus destination.

<figure><img src="https://github.com/observIQ/bindplane-docs/blob/main/.gitbook/assets/release-notes-bindplane-2025-01-22-release-image-3.png" alt="Bindplane docs - 2025-01-22-Release - image 3"><figcaption></figcaption></figure>


---

# 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/january-2025/2025-01-22-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.