> 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/oct-2026/2026-10-14-v1.104.0.md).

# Oct 14, 2026 - v1.104.0

Self-hosted

#### New features and improvements

* **Data Flow page:** a new page that is now the default Overview.
* **Collector upgrades:** you can upgrade disconnected collectors. The upgrade is delivered when the collector reconnects.
* **Full Pipeline Blueprints:** configuration resources now appear in the dropdown, and a blueprint can be connected when you add it to a configuration.
* **REST API source:** adds TLS, LRO, and raw options, `has_more`, `offset_type` and `page_size` fields, fractional epoch seconds, POST polling, and a request preview.
* **Other sources:**
  * Bindplane Collector source v2, with per-metric toggles and exposed filelog parameters.
  * v2 S3/GCS event sources (v1 is deprecated).
  * Azure Event Hub Kubernetes Gateway source.
  * Azure Blob Polling gets blob format and incremental read options.
  * The OTLP receiver now exposes `enforcement_policy`.
* **CLI:** `bindplane get configuration --include-dependencies`.
* **Performance:** configuration history loads faster.
* **UI:** The organization switcher now sits above account management.

#### Bug fixes

* **Collector connections:**
  * Agent labels are kept across chained reassignments.
  * v2 agents are registered under their instance UID.
* **Configurations:**
  * Rollout options no longer open after a rollback.
* **Google Cloud:** service attributes are dropped from collector self-metrics.
* **UI:**
  * Fixed the “Something went wrong” Privacy Policy error in some onboarding flows.
  * Fixed gateway naming and the cluster/workload links on the Gateway page.
  * Azure Blob Polling advanced options have a cleaner layout.


---

# 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/oct-2026/2026-10-14-v1.104.0.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.
