Documentation

Create agents in 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

Agents represent Telegraf instances that send heartbeat data to Telegraf Controller through the heartbeat output plugin. Controller uses the heartbeat payload to create and track each agent.

How agent creation works

  • The heartbeat output plugin in a Telegraf configuration reports agent data back to the /agents/heartbeat endpoint of your Telegraf Controller instance.
  • The heartbeat payload includes a unique instance_id (also referred to as an “agent ID”) for the agent.
  • When the first heartbeat arrives for an agent, Telegraf Controller automatically creates the agent record and marks it with the reported status. Subsequent agent heartbeats update the existing agent record.

Configure agents

Heartbeat output plugin configuration options determine what agent data Telegraf sends to Telegraf Controller. The following heartbeat plugin configuration options are available:

  • url: (Required) URL of heartbeat endpoint.
  • instance_id: (Required) Unique identifier for the Telegraf instance or agent (also known as the agent ID).
  • token: (Required with auth enabled) Telegraf Controller API token for the heartbeat endpoint. The token must have write permissions on the Heartbeat API.
  • interval: Interval for sending heartbeat messages. Default is 1m (every minute).
  • include: Information to include in the heartbeat message. Available options are:
    • hostname: Hostname of the machine running Telegraf.
    • statistics: (Recommended) Agent metrics including number of metrics collected and written since the last heartbeat, logged error and warning counts, etc.
    • configs: (Recommended) Redacted list of configurations loaded by the Telegraf instance.
  • headers: HTTP headers to include with the heartbeat request.

Example heartbeat output plugin

The following is an example heartbeat output plugin configuration that uses an agent_id configuration parameter to specify the instance_id.

[[outputs.heartbeat]]
  url = "http://telegraf_controller.example.com/agents/heartbeat"
  instance_id = "&{agent_id}"
  token = "${INFLUX_TOKEN}"
  interval = "1m"
  include = ["hostname", "statistics", "configs"]

  [outputs.heartbeat.headers]
    User-Agent = "telegraf"

Authorize heartbeats using an API token

If Telegraf Controller requires authorization on the Heartbeat API, include the token option in your heartbeat plugin configuration. Provide a Telegraf Controller token with write permissions on the Heartbeat API.

We recommend defining the INFLUX_TOKEN environment variable when starting Telegraf and using that to define the token in your heartbeat plugin.

Verify a new agent

  1. Open Telegraf Controller and go to Agents.
  2. Confirm the agent appears in the list with the expected instance_id.
  3. Click the More button () and select View Details to verify metadata, labels, and the reporting rule assignment.

Was this page helpful?

Thank you for your feedback!


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