Documentation

Manage settings

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

Owners and administrators can configure authentication, login security, and password requirements for Telegraf Controller.

Navigate to the Settings page from the left navigation menu to view and modify these settings.

Telegraf Controller settings page

Require authentication per endpoint

Telegraf Controller organizes API endpoints into groups. Authentication can be required or disabled for each group independently, giving you fine-grained control over which resources require credentials.

Endpoint groupCovers
agentsAgent monitoring and management
configsConfiguration management
labelsLabel management
reporting-rulesReporting rule management
heartbeatAgent heartbeat requests

When authentication is disabled for a group, anyone with network access can use those endpoints without an API token. When enabled, requests require valid authentication.

By default, authentication is required for all endpoints.

To toggle authentication for endpoint groups:

  1. Navigate to the Settings page.
  2. Toggle authentication on or off for each endpoint group.
  3. Click Save.

Disabling authentication for endpoints means anyone with network access to Telegraf Controller can access those resources without credentials.

Environment variable and CLI flag

You can configure disabled authentication endpoints at startup using the DISABLED_AUTH_ENDPOINTS environment variable or the --disable-auth-endpoints CLI flag. The value is a comma-separated list of endpoint groups, or "*" to disable authentication for all endpoints.

# Disable auth for agents and heartbeat only
export DISABLED_AUTH_ENDPOINTS="agents,heartbeat"

# Disable auth for all endpoints
export DISABLED_AUTH_ENDPOINTS="*"

Using the CLI flag:

# Disable auth for agents and heartbeat only
./telegraf_controller --disable-auth-endpoints=agents,heartbeat

# Disable auth for all endpoints
./telegraf_controller --disable-auth-endpoints="*"

These values are used as initial defaults when Telegraf Controller creates its settings record for the first time. After that, changes made through the Settings page take precedence.

Login security

Login attempts

You can configure the number of failed login attempts allowed before an account is locked out. The default threshold is 5 attempts, with a minimum of 1.

To change the login attempt threshold:

  1. Navigate to the Settings page.
  2. Update the Login attempts value.
  3. Click Save.

Login lockout

When a user exceeds the failed attempt threshold, their account is locked for a configurable duration. The default lockout duration is 15 minutes, with a minimum of 1 minute. The lockout clears automatically after the configured duration has elapsed.

To change the lockout duration:

  1. Navigate to the Settings page.
  2. Update the Login lockout duration value.
  3. Click Save.

If a user is locked out, an owner or administrator can reset their password to unlock the account.

Password complexity requirements

Telegraf Controller provides three password complexity levels that apply to all password operations, including initial setup, password changes, password resets, and invite completion.

LevelMin lengthUppercase*Lowercase*Digits*Special characters*
Low8NoNoNoNo
Medium10YesYesYesNo
High12YesYesYesYes

* Passwords require at least one of the defined character types.

To change the password complexity level:

  1. Navigate to the Settings page.
  2. Select the desired Password complexity level.
  3. Click Save.

Changing the password complexity level does not affect existing passwords. The new requirements apply only when users set or change their passwords.

Environment variables

You can set initial defaults for login security settings using environment variables. These values are applied when Telegraf Controller initializes its settings for the first time. Changes made on the Settings page override initialized settings.

Environment variableDescriptionDefault
LOGIN_LOCKOUT_ATTEMPTSFailed attempts before lockout5
LOGIN_LOCKOUT_MINUTESMinutes to lock account15
PASSWORD_COMPLEXITYComplexity level (low, medium, high)low

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