Documentation

Telegraf Controller

Set agent statuses

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.

Agent statuses come from the Telegraf heartbeat output plugin and are sent with each heartbeat request. The plugin reports an ok status.

A future Telegraf release will let you configure logic that sets the status value. Telegraf Controller also applies reporting rules to detect stale agents. If an agent does not send a heartbeat within the rule’s threshold, Controller marks the agent as Not Reporting until it resumes sending heartbeats.

View an agent’s status

  1. In Telegraf Controller, go to Agents.
  2. Check the Status column for each agent.
  3. To see more details, click the More button (⋮) and select View Details.
  4. The details page shows the reported status, reporting rule assignment, and the time of the last heartbeat.

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