Documentation

View and update a Telegraf Enterprise license

After a Telegraf Enterprise license is applied to Telegraf Controller, use the user interface (UI) or API to inspect the license, monitor entitlements and usage, replace the license at renewal, or remove the license to revert to the free tier.

Telegraf Enterprise

Unlock higher configuration and agent limits, enhanced security features, and official support for Telegraf and Telegraf Controller.

View the current license

In the UI, navigate to Settings > Enterprise to view:

  • License ID: the unique identifier for your license. Include this value when contacting InfluxData support.
  • Loaded: the date and time the license was applied to this Telegraf Controller instance.
  • Expires: the contractual expiration date, with a status chip indicating current state (valid, expiring, or expired).
  • Max configurations: the configurations entitlement from the license.
  • Max reporting agents: the reporting agents entitlement from the license.
Telegraf Enterprise license details in Telegraf Controller

From the API, an Owner can call GET /api/license to retrieve the same information for scripted checks:

curl -H "Authorization: Bearer 
YOUR_TC_API_TOKEN
"
\
https://telegraf_controller.example.com/api/license

Replace YOUR_TC_API_TOKEN with your Telegraf Controller API token.

Example response:

{
  "status": "valid",
  "licenseId": "Xxxx0oXx-Xx0o-00Xx-oXxX-xX0oXx0oXx0o",
  "issuedAt": "2024-01-15T10:00:00Z",
  "expiresAt": "2026-12-31T00:00:00Z",
  "maxConfigs": 100000,
  "maxAgents": 18000,
  "loadedAt": "2024-06-01T14:30:00Z"
}

If no license is applied, GET /api/license returns 404 Not Found.

View entitlements and usage

Any authenticated user can call GET /api/license/entitlements to see the effective entitlements alongside current usage. This endpoint is the right choice for monitoring dashboards and capacity-planning scripts because it doesn’t require the Owner role and works on both licensed and unlicensed instances.

curl -H "Authorization: Bearer 
YOUR_TC_API_TOKEN
"
\
https://telegraf_controller.example.com/api/license/entitlements

Replace YOUR_TC_API_TOKEN with your Telegraf Controller API token.

Example response on a licensed instance:

{
  "status": "valid",
  "licenseId": "Xxxx0oXx-Xx0o-00Xx-oXxX-xX0oXx0oXx0o",
  "expiresAt": "2026-12-31T00:00:00Z",
  "enterpriseEnabled": true,
  "entitlements": {
    "maxConfigs": 100000,
    "maxAgents": 18000
  },
  "usage": {
    "configs": 47,
    "agents": 183
  }
}

Example response on an unlicensed instance:

{
  "status": "unlicensed",
  "licenseId": null,
  "expiresAt": null,
  "enterpriseEnabled": false,
  "entitlements": {
    "maxConfigs": 20,
    "maxAgents": 100
  },
  "usage": {
    "configs": 8,
    "agents": 12
  }
}

Replace a license

To apply a renewed or upgraded license, apply the new license through Settings > Enterprise exactly the same way you applied the first one. Telegraf Controller validates the new license and replaces the existing one in place. The new entitlements take effect immediately with no restart.

Failed license updates never downgrade a valid license

If the new license fails validation, Telegraf Controller retains the previously active license and returns an error describing the validation failure. Your enterprise features and scale limits are unaffected. See Troubleshoot licensing for the error catalog.

Remove a license

Removing a license reverts Telegraf Controller to the free tier. Only the Owner can remove a license.

  1. Navigate to Settings > Enterprise.

  2. Click Remove license.

  3. Confirm the action in the dialog.

    Confirm that you want to remove your Telegraf Enterprise license

The change takes effect immediately, with no restart required.

After removal:

  • Scale limits revert to the free tier: 20 configurations and 100 reporting agents.
  • Enterprise features are disabled: audit logging, LDAP authentication, and OIDC authentication stop accepting new requests.
  • Existing resources above the free-tier limit are preserved but cannot grow. Create requests for configurations or agent registrations are rejected with 402 Payment Required until usage drops below the free-tier limit.
  • Existing IdP-authenticated sessions remain valid until they expire on their own. New LDAP or OIDC logins are blocked. Local authentication becomes the only authentication method for the UI. For users that only used IdP authentication and do not have a configured password, an Owner or Administrator must initiate a password reset for that user.

To restore enterprise features and licensed entitlements, apply a license again. See Apply a license.


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