Documentation

Remove a Telegraf configuration

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

Use the InfluxDB user interface (UI) or the influx CLI to remove Telegraf configurations from InfluxDB.

Deleting a Telegraf configuration does not affect running Telegraf agents. However, if an agents stops, it needs a new configuration to start.

To remove a Telegraf configuration, do one of the following:

Use the InfluxDB UI

  1. In the navigation menu on the left, select Data (Load Data) > Telegraf.

  2. Hover over the configuration you want to delete, click the icon, and then click Delete.

Use the influx CLI

Use the influx telegrafs rm command to remove a Telegraf configuration from InfluxDB.

Provide the following:

  • Telegraf configuration ID (shown in the output of influx telegrafs)
# Syntax
influx telegrafs rm -i <telegraf-config-id>

# Example
influx telegrafs rm -i 12ab34de56fg78hi

Was this page helpful?

Thank you for your feedback!


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:

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 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