Documentation

Delete configurations

Telegraf Controller is in Private Alpha

Telegraf Controller is in private alpha. If you are interested in being a part of the private alpha program, please sign up:

Sign Up for the Alpha

While in alpha, 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.

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!


New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

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:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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