Documentation

Agent status evaluation

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

The Telegraf heartbeat output plugin uses CEL expressions to evaluate agent status based on runtime data such as metric counts, error rates, and plugin statistics. CEL (Common Expression Language) is a lightweight expression language designed for evaluating simple conditions.

How status evaluation works

You define CEL expressions for three status levels in the [outputs.heartbeat.status] section of your Telegraf configuration:

  • ok — The agent is healthy.
  • warn — The agent has a potential issue.
  • fail — The agent has a critical problem.

Each expression is a CEL program that returns a boolean value. Telegraf evaluates expressions in a configurable order (default: ok, warn, fail) and assigns the status of the first expression that evaluates to true.

If no expression evaluates to true, the default status is used (default: "ok").

Initial status

Use the initial setting to define a status before the first Telegraf flush cycle. If initial is not set or is empty, Telegraf evaluates the status expressions immediately, even before the first flush.

Evaluation order

The order setting controls which expressions are evaluated and in what sequence.

If you omit a status from the order list, its expression is not evaluated.

Configuration reference

Configure status evaluation in the [outputs.heartbeat.status] section of the heartbeat output plugin. You must include "status" in the include list for status evaluation to take effect.

[[outputs.heartbeat]]
  url = "http://telegraf_controller.example.com/agents/heartbeat"
  instance_id = "agent-123"
  interval = "1m"
  include = ["hostname", "statistics", "status"]

  [outputs.heartbeat.status]
    ## CEL expressions that return a boolean.
    ## The first expression that evaluates to true sets the status.
    ok = "metrics > 0"
    warn = "log_errors > 0"
    fail = "log_errors > 10"

    ## Evaluation order (default: ["ok", "warn", "fail"])
    order = ["ok", "warn", "fail"]

    ## Default status when no expression matches
    ## Options: "ok", "warn", "fail", "undefined"
    default = "ok"

    ## Initial status before the first flush cycle
    ## Options: "ok", "warn", "fail", "undefined", ""
    # initial = ""
OptionTypeDefaultDescription
okstring (CEL)"false"Expression that, when true, sets status to ok.
warnstring (CEL)"false"Expression that, when true, sets status to warn.
failstring (CEL)"false"Expression that, when true, sets status to fail.
orderlist of strings["ok", "warn", "fail"]Order in which expressions are evaluated.
defaultstring"ok"Status used when no expression evaluates to true. Options: ok, warn, fail, undefined.
initialstring""Status before the first flush. Options: ok, warn, fail, undefined, "" (empty = evaluate expressions).

Was this page helpful?

Thank you for your feedback!


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:

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