Documentation

Telegraf Controller

Manage Telegraf agents

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 tracks agents that send heartbeats through the Telegraf heartbeat output plugin. Each heartbeat includes a unique instance_id (also called “agent ID”) so Controller can distinguish one agent from another.

  • Telegraf Controller automatically creates agents the first time a heartbeat arrives from a unique agent.
  • Click the More button (⋮) in the agent list and select View Details to see information and reporting history for an agent.
  • Reporting rules define how long an agent can go without sending a heartbeat before Controller marks it as Not Reporting. They can also automatically delete agents that haven’t reported in a specified amount of time.
  • You can assign a reporting rule from the agent list or an agent details page.

Create agents

Learn how Telegraf Controller creates agents from heartbeat plugin reports and how to verify new agents in the UI.

Define agent reporting rules

Define reporting rules that determine when Telegraf Controller marks agents as not reporting and optionally automatically delete not reporting agents.

Set agent statuses

Understand how Telegraf Controller receives and displays agent statuses from the heartbeat output plugin.

Delete agents

Remove individual or multiple Telegraf agents from Telegraf Controller.

Was this page helpful?

Thank you for your feedback!

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

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