Documentation

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

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

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!


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