Documentation

Revoke a token

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

Revoking a token immediately prevents it from being used for authentication while keeping the token record in the system for auditing purposes. Unlike deletion, revocation preserves a full history of the token, including when it was created and when it was disabled.

Revoke versus delete

Telegraf Controller supports two ways to remove a token from active use: revocation and deletion.

  • Revoked tokens remain visible in the token list with a Revoked status. This provides an audit trail showing when the token was created and when it was disabled. Revoked tokens cannot be used for authentication.
  • Deleted tokens are permanently removed from the system. No record of the token is retained after deletion.

Use revoke when you want to disable a token but maintain an audit trail. Use delete when you want to completely remove the token and its record from the system.

For more information about deleting a token, see Delete a token.

Revoke a token

  1. Navigate to the API Tokens page, or open the token’s detail view.
  2. Click Revoke. If on the token detail page, select the Manage tab to reveal the Revoke action.
  3. Confirm the revocation in the dialog.

The token status changes to Revoked and any requests that use the token are immediately rejected.

You cannot reactivate a revoked token

Revocation is permanent. You cannot re-activate a revoked token. If you need to restore access, create a new token. See Create a token.

Bulk revoke

To revoke multiple tokens at once:

  1. On the API Tokens page, select the tokens you want to revoke.
  2. Click Revoke in the bulk actions bar.
  3. Confirm the revocation in the dialog.

All selected tokens are immediately revoked and can no longer be used for authentication.


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