Documentation

influx config

The influx config command displays the active InfluxDB connection configuration and manages multiple connection configurations stored, by default, in ~/.influxdbv2/configs. Each connection includes a URL, token, associated organization, and active setting. InfluxDB reads the token from the active connection configuration, so you don’t have to manually enter a token to log into InfluxDB.

Usage

influx config [flags]
influx config [command]
influx config <config-name>
Quickly switch between configurations
# Syntax
influx config <config-name>

# Example
influx config local-config

To quickly switch back to the previous configuration, use the following command:

influx config -

Examples

# Show the active connection configuration
influx config

# Set a connection configuration as active
influx config local-config

Subcommands

SubcommandDescription
createCreate a connection configuration
listList connection configurations
deleteDelete a connection configuration
setSet or update a connection configuration

Flags

FlagDescription
-h--helpHelp for the config command

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:

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

InfluxDB Cloud Serverless