Documentation

Delete agents from Telegraf Controller

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.

Remove individual or multiple Telegraf agents from Telegraf Controller.

Deleting an agent from Telegraf Controller does not affect the running Telegraf instance; it only deletes the record of the agent from Telegraf Controller.

Delete a single agent

  1. In Agents, find the agent you want to remove.
  2. Click the More button () and select Delete Agent.
  3. Confirm the deletion.

Delete multiple agents

  1. In Agents, select the checkboxes for the agents you want to remove.
  2. Select Delete Agents.
  3. Confirm the deletion.

Automatically delete agents

Use reporting rules to automatically delete agents that have not reported in a specified amount of time.

  1. Create a reporting rule with auto-delete enabled.
  2. Assign the newly created rule to agents.

If agents assigned to the reporting rule do not report in the defined auto-delete threshold, they are automatically deleted.


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