Documentation

Telegraf Controller

Uninstall Telegraf Controller

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

Uninstall Telegraf Controller and remove all files associated with the application. This process depends on your operating system and installation method.

Linux macOS Windows

Linux

To fully uninstall Telegraf Controller from Linux:

  1. Stop Telegraf Controller:

    • If running the application in place, stop the telegraf_controller process.

    • If you installed Telegraf Controller as a systemd service stop and disable the service:

      sudo systemctl stop telegraf-controller
sudo systemctl disable telegraf-controller

  2. Remove all files associated with Telegraf Controller:

    # Remove the telegraf_controller executable
sudo rm -rf /opt/telegraf-controller

# Remove the telegraf_controller shared directory, which includes the
# SQLite database if using SQLite
rm -rf ~/.local/share/telegraf_controller

# Remove the service file if you installed Telegraf Controller as a service
sudo rm /etc/systemd/system/telegraf-controller.service

  3. If using PostgreSQL, delete the telegraf_controller database from your PostgreSQL instance:

    DROP DATABASE telegraf_controller;

macOS

To fully uninstall Telegraf Controller from macOS:

  1. Stop Telegraf Controller:

    • If running the application in place, stop the telegraf_controller process.

    • If you installed Telegraf Controller as a macOS LaunchDaemon and are running it as a service, stop the service:

      sudo launchctl unload /Library/LaunchDaemons/com.influxdata.telegraf-controller.plist

  2. Remove all files associated with Telegraf Controller:

    # Remove the telegraf_controller executable
sudo rm /usr/local/bin/telegraf_controller

# Remove the telegraf_controller application directory, which includes the
# SQLite database if using SQLite
rm -rf ~/Library/Application\ Support/telegraf_controller

# Remove the plist file if you installed Telegraf Controller as a LaunchDaemon
sudo rm /Library/LaunchDaemons/com.influxdata.telegraf-controller.plist

  3. If using PostgreSQL, delete the telegraf_controller database from your PostgreSQL instance:

    DROP DATABASE telegraf_controller;

Windows

To fully uninstall Telegraf Controller from Windows:

  1. Stop Telegraf Controller:

    • If running the application in place, stop the telegraf_controller process.

    • If you installed Telegraf Controller as a service, stop and remove the service:

      nssm stop TelegrafController
nssm remove TelegrafController confirm

  2. Remove all files associated with Telegraf Controller:

    # Remove the telegraf_controller executable and other related files,
# including the SQLite database if using SQLite
Remove-Item -Path "$env:LOCALAPPDATA\telegraf_controller" -Recurse
Remove-Item -Path "C:\Program Files\TelegrafController" -Recurse

  3. If using PostgreSQL, delete the telegraf_controller database from your PostgreSQL instance:

    DROP DATABASE telegraf_controller;

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

  • InfluxDB Cloud
  • InfluxDB OSS or Enterprise
AWS

  • US West (Oregon)

GCP
Azure
Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

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