Documentation

Manage users

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

Users are accounts that can log into the Telegraf Controller web interface and interact with the system based on their assigned role. You can create, update, disable, and delete users to control who has access to your Telegraf Controller instance.

User states

Each user account is in one of the following states:

  • Active — The user can log in and perform actions based on their assigned role.
  • Disabled — The user cannot log in. Existing API tokens remain associated with the account but are unusable while the user is disabled.
  • Locked — A temporary state triggered by too many failed login attempts. The lock clears automatically after the configured lockout period. See the Settings page for configuration options.

User roles

Telegraf Controller supports four roles with different levels of access:

RoleAccess level
OwnerFull access. Manages users, tokens, and settings.
AdministratorFull access except ownership transfer.
ManagerManages configs, agents, labels, reporting rules, and own tokens.
ViewerRead-only access.

For more details about roles and permissions, see Authorization.


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