docs-v2/data/notifications.yaml

# Notification data structure
#
# - id: unique ID for notification, cannot start with digit, no spaces, a-z and 0-9
#   level: note or warn
#   scope:
#     - list of URL paths to show the notification on, no scope shows everywhere
#   exclude:
#     - list of URL paths to not show the notification on
#   title_tag: (optional) Tag to include before the notification title
#   title: Message title
#   slug: (optional) Short notification summary
#   message: |
#     Markdown message content.

# - id: future-of-flux-new
#   level: note
#   scope:
#     - /flux/v0
#     - /influxdb/v1/flux/
#     - /influxdb/v2/query-data/get-started/
#     - /influxdb/cloud/query-data/get-started/
#   exclude:
#     - /flux/v0/future-of-flux/
#   title: The future of Flux
#   slug: |
#     Flux is going into maintenance mode. You can continue using it as you
#     currently are without any changes to your code.
#
#     [Read more](/flux/v0/future-of-flux)
#   message: |
#     Flux is going into maintenance mode and will not be supported in InfluxDB 3.0.
#     This was a decision based on the broad demand for SQL and the continued growth
#     and adoption of InfluxQL. We are continuing to support Flux for users in 1.x
#     and 2.x so you can continue using it with no changes to your code.
#     If you are interested in transitioning to InfluxDB 3.0 and want to
#     future-proof your code, we suggest using InfluxQL.
#
#     For information about the future of Flux, see the following:
#
#     - [The plan for InfluxDB 3.0 Open Source](https://influxdata.com/blog/the-plan-for-influxdb-3-0-open-source)
#     - [InfluxDB 3.0 benchmarks](https://influxdata.com/blog/influxdb-3-0-is-2.5x-45x-faster-compared-to-influxdb-open-source/)

- id: influxdb3-9-performance-preview
  level: note
  scope:
    - /influxdb3/enterprise/
  exclude:
    - /influxdb3/enterprise/performance-preview/
  title: 'InfluxDB 3.9: Performance upgrade preview'
  slug: |
    InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades
    with faster single-series queries, wide-and-sparse table support, and more.    

  message: |
    InfluxDB 3 Enterprise 3.9 includes a beta of major performance and
    feature updates.

    **Key improvements:**

    - Faster single-series queries
    - Consistent resource usage
    - Wide-and-sparse table support
    - Automatic distinct value caches for reduced latency with metadata queries

    _Preview features are subject to breaking changes._

    For more information, see:

    - [Performance upgrade preview](/influxdb3/enterprise/performance-preview/)
    - [InfluxDB 3 Enterprise release notes](/influxdb3/enterprise/release-notes/)
    - [InfluxData Blog post](https://www.influxdata.com/blog/influxdb-3-9/)    

- id: telegraf-enterprise-beta
  level: note
  scope:
    - /
  exclude:
    - /platform/
    - /resources/
    - /kapacitor/
    - /chronograf/
    - /enterprise_influxdb/
    - /influxdb3/
    - /influxdb/
    - /flux/
  title: Telegraf Enterprise now in public beta
  slug: |   
    Get early access to the **Telegraf Controller** and provide feedback to help
    shape the future of **Telegraf Enterprise**.

    <a class="btn" href="https://www.influxdata.com/blog/telegraf-enterprise-beta">See the Blog Post</a>
  message: |
    The upcoming Telegraf Enterprise offering is for organizations running
    Telegraf at scale and is comprised of two key components:

    - **Telegraf Controller**: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
    - **Telegraf Enterprise Support**: Official support for Telegraf Controller and Telegraf plugins.

    <a href="https://influxdata.com/products/telegraf-enterprise" target="_blank">Join the Telegraf Enterprise beta</a>
    to get early access to the Telegraf Controller and provide feedback to help
    shape the future of Telegraf Enterprise.

    For more information:

    - [See the announcement blog post](https://www.influxdata.com/blog/telegraf-enterprise-beta)
    - [Telegraf Controller Documentation](/telegraf/controller/)
    - [Download and install Telegraf Controller](/telegraf/controller/install/)    

# - id: influxdb3.8-explorer-1.6
#   level: note
#   scope:
#     - /
#   title: New in InfluxDB 3.8
#   slug: |
#     Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

#     <a class="btn" href="https://www.influxdata.com/blog/influxdb-3-8/">See the Blog Post</a>
#   message: |
#     InfluxDB 3.8 is now available for both Core and Enterprise, alongside the
#     1.6 release of the InfluxDB 3 Explorer UI. This release is focused on
#     operational maturity and making InfluxDB easier to deploy, manage, and run
#     reliably in production.

#     For more information, check out:

#     - [See the announcement blog post](https://www.influxdata.com/blog/influxdb-3-8/)
#     - [InfluxDB 3 Core release notes](/influxdb3/core/release-notes/)
#     - [InfluxDB 3 Enterprise release notes](/influxdb3/enterprise/release-notes/)

- id: influxdb-docker-latest-tag-apr
  level: warn
  scope:
    - /
  exclude:
    - /telegraf/
    - /platform/
    - /kapacitor/
    - /chronograf/
    - /enterprise_influxdb/
    - /influxdb3/explorer/
    - /influxdb3/cloud
    - /influxdb/cloud
  title: InfluxDB Docker latest tag changing to InfluxDB 3 Core
  slug: |
    On **May 27, 2026**, the `latest` tag for InfluxDB Docker images will
    point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version
    tags in your Docker deployments.    
  message: |
    If using Docker to install and run InfluxDB, the `latest` tag will point to
    InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in
    your Docker deployments. For example, if using Docker to run InfluxDB v2,
    replace the `latest` version tag with a specific version tag in your Docker
    pull command--for example:

    ```sh
    docker pull influxdb:2
    ```