Documentation

Delete configurations

Telegraf Controller is in Public Beta

Telegraf Controller is in public beta and will be part of the future Telegraf Enterprise offering. While in beta, Telegraf Controller is not meant for production use. The Telegraf Controller documentation is a work in progress, and we are actively working to improve it. If you have any questions or suggestions, please submit an issue. We welcome any and all contributions.

Beta expectations

Provide beta feedback

Delete configurations you no longer use to keep Telegraf Controller organized.

Deleting a configuration permanently removes it from Telegraf Controller. Export the TOML if you need a backup.

Before you delete

You cannot delete a configuration that is currently used by actively reporting agents. To delete a configuration:

  • Confirm no agents rely on the configuration.
  • Delete agents or reassign agents to another configuration if needed.

Delete a single configuration

Delete configuration from either the configurations list page or the configuration detail page.

From the configurations list page

  1. In the Telegraf Controller web interface, select Configurations in the navigation bar.
  2. Click the More button () next to the configuration you want to delete and select Delete.
  3. Confirm the deletion.

From the configuration detail page

  1. In the Telegraf Controller web interface, select Configurations in the navigation bar.
  2. Click the name of the configuration you want to delete to view the configuration detail page.
  3. Select the Manage tab.
  4. Under Delete Configuration, click Delete.
  5. Confirm the deletion.

Delete multiple configurations

  1. In the Telegraf Controller web interface, select Configurations in the navigation bar.
  2. Use the select boxes to select all of the configurations you want to delete.
  3. In the bulk options menu that appears, click Delete.
  4. Confirm the deletion.

Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

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:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

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.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

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.

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:

docker pull influxdb:2