Documentation

Telegraf Enterprise

Telegraf Enterprise

Telegraf Enterprise is the commercial package for organizations running Telegraf and Telegraf Controller at scale. It combines higher Telegraf Controller limits, enterprise authentication and audit logging, and an enterprise support contract from InfluxData covering both the Telegraf agent and Telegraf Controller.

Purchase Telegraf Enterprise

What’s included

Enterprise support for Telegraf and Telegraf Controller

Telegraf Enterprise includes an enterprise support contract from InfluxData covering both the open source Telegraf agent and Telegraf Controller. For details on support coverage and SLAs, contact InfluxData.

Higher scale limits in Telegraf Controller

Telegraf Enterprise raises the per-instance limits on configurations and reporting agents that Telegraf Controller can manage. The exact limits are defined in your license and are part of your contract. See Free tier and Enterprise comparison for the free-tier defaults.

Enterprise features in Telegraf Controller

A Telegraf Enterprise license unlocks the following features in Telegraf Controller:

  • Audit logging: Tamper-evident log of administrative actions performed in Telegraf Controller.
  • LDAP authentication: Authenticate Telegraf Controller users against an LDAP directory.
  • OIDC authentication: Single sign-on through OpenID Connect providers such as Okta, Auth0, and Microsoft Entra ID.

Free tier and Enterprise comparison

Telegraf Controller runs in a free tier suitable for evaluation and small deployments when no license is applied.

Free tierTelegraf Enterprise
Configurations20Defined per contract
Reporting agents100Defined per contract
Audit logging—Included
LDAP authentication—Included
OIDC authentication—Included
Local authentication and API tokensIncludedIncluded
User management (RBAC)IncludedIncluded
SupportCommunityEnterprise support contract

How licensing works

Licenses are signed JSON Web Tokens (JWTs) issued by InfluxData. Telegraf Controller validates licenses in both connected and air-gapped environments.

A Telegraf Controller instance has one active license at a time. Replacing a license takes effect immediately, with no restart required.

Telegraf Controller accepts a license two ways:

  • At startup using the LICENSE_FILE_PATH environment variable. Preferred for automated and infrastructure-as-code deployments.
  • At runtime by uploading the license through the Telegraf Controller user interface. Preferred for interactive setup.

The Owner role is required to apply, replace, or remove a license. Any authenticated user can view the current entitlements and usage.

License lifecycle

A license moves through the following states as its expiration date approaches:

StateWhenBehavior
UnlicensedNo license appliedFree-tier limits apply; enterprise features are disabled.
ValidLicense is active and more than 30 days from expirationLicensed entitlements apply; enterprise features are enabled.
ExpiringLicense expires within 30 daysLicensed entitlements still apply; an informational banner appears in the UI.
Grace PeriodLicense has expired but less than 15 days have elapsedLicensed entitlements still apply; an error banner appears in the UI.
ExpiredLicense expired 15 or more days agoLimits revert to the free tier; enterprise features are disabled.

For full details on what changes at each stage, including the API status names for each state (such as expired_grace), see License enforcement.

How to obtain Telegraf Enterprise

To purchase Telegraf Enterprise or request an evaluation license, contact InfluxData sales. InfluxData issues a license file that you apply to your Telegraf Controller instance.

Next steps

If you already have a license file:

If you’re evaluating:

Was this page helpful?

Thank you for your feedback!

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

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