Documentation

Define agent reporting rules

Reporting rules define how long an agent can go without sending a heartbeat before Telegraf Controller changes its status to Not Reporting. They can also automatically delete agents that haven’t reported in a specified amount of time.

Telegraf Controller requires a default reporting rule. Newly created agents are automatically assigned to the current default reporting rule.

Manage reporting rules in the Reporting Rules section of Controller, then assign them to agents from either the agent list or an agent details page.

Create a reporting rule

  1. In Telegraf Controller, go to Reporting Rules.
  2. Select + Add Rule.
  3. Enter the following:
    • Description: Reporting rule description
    • Not Reporting Threshold: The maximum time an agent can go without reporting before Controller assigns the “Not Reporting” status.
    • Auto-delete agents: Enable to automatically delete agents that haven’t reported in the defined auto-delete threshold.
    • Default Rule: Enable to make the rule the default reporting rule.
  4. Save the rule.

Update a reporting rule

  1. In Reporting Rules, click the More button () of the rule you want to update.
  2. Select Edit.
  3. Edit the description, not reporting threshold, auto-delete settings, or make the rule the default reporting rule.
  4. Save your changes.

Delete a reporting rule

  1. In Reporting Rules, click the More button () of the rule you want to delete.
  2. Select Delete and confirm.

You cannot delete the default reporting rule

To delete a reporting rule that is currently the default rule, first assign a new rule as the default reporting rule.

Agents assigned to a deleted reporting rule

When you delete a reporting rule, any agents assigned to the deleted rule automatically inherit the default reporting rule.

Set a default reporting rule

From the reporting rules list

  1. In Reporting Rules, click the More button () of the rule you want to make the default.
  2. Select Make Default.

From reporting rule details

  1. In Reporting Rules, click the More button () of the rule you want to make the default.
  2. Select Edit.
  3. Toggle Default Rule to true.
  4. Save your changes.

Assign a reporting rule to agents

From the agent list

  1. In Agents, select one or more agents.
  2. Select Assign Rule.
  3. Choose a rule and assign it.

From an agent details page

  1. In Agents, click the More button () for an agent and select View Details.
  2. In the Reporting Rule section, select Change.
  3. Choose a rule and apply it.

Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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