> 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-12-release.md). # 2024-06-12-Release Version 1.59.0 • JUN 12, 2024 ## New Features * [Organizations and Projects](#organizations-and-projects) * New Kubernetes Prometheus source * Detect and scrape Prometheus exporters using Prometheus Kubernetes service discovery. ## Bug Fixes * Google Cloud destination: Set location resource if not already set * Resolves an issue where Google rejects metric types that require a location. * Audit log CSV exporter now respects users timezone * Require configuration match labels * If match labels are not present, `configuration=` will be added automatically when creating a configuration using the API. ## Other * Agent's telemetry port `8888` will now bind to `localhost` on Linux, Windows, and macOS. * Deprecated Filter by Field processor in favor of [Filter by Condition](https://github.com/observIQ/bindplane-docs/blob/main/integrations/processors/filter-by-condition.md) processor ## Organizations and Projects Starting in 1.59 each deployment of BindPlane OP will have a new top-level Organization made up of\ all the previous existing Accounts on the deployment. Accounts will now be referred to as Projects,\ which still contain all of the Agents and Resources associated with the account. Some things to note: * Any previous Admin level users now also receive the Organization Admin role. Organization admins can see all projects in an organization and any user that uses those projects. * Organization Admins can access the new Organization page found in the settings menu. * New Project creation is now limited to Organization Admins only. --- # 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-12-release.md?ask=&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.