Documentation

Telegraf Controller documentation

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.

Telegraf Controller is a centralized application for managing Telegraf deployments at scale. Use it to define configurations once and apply them consistently across fleets of agents. Monitor agent health and roll out updates without manually editing individual agents.

Key features

  • Create and manage agent configurations
  • Connect agents to Telegraf Controller
  • Monitor the overall health of your agent deployment
  • Roll out changes safely and verify agent status
  • Apply custom logic to agents to identify when they are considered “not reporting”
Telegraf Controller agent summary

Configuration and agent workflow

  • Create and store Telegraf configurations in Telegraf Controller
  • Start a Telegraf agent, pulling its configuration from Telegraf Controller, and have it regularly check for configuration updates.
  • Agents use the Telegraf Heartbeat output plugin (available with Telegraf v1.37+) to report their status back to Telegraf Controller
  • Telegraf Controller provides agent-specific and deployment-wide health information.
  • When you update a configuration, agents see the change and load the updated configuration.

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