Documentation

influx server-config

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

The influx server-config command displays the InfluxDB runtime server configuration.

To display the server configuration, you must use an operator token.

Usage

influx server-config [flags]
influx server-config [command]

Examples

# Show the server configuration.
influx server-config

# Show the server configuration as YAML.
influx server-config --yaml

Flags

FlagDescription
-c--active-configCLI configuration to use for command
--configs-pathPath to influx CLI configurations (default ~/.influxdbv2/configs)
-h--helpHelp for the list command
--hide-headersHide table headers (default false)
--hostHTTP address of InfluxDB (default http://localhost:8086)
--http-debugInspect communication with InfluxDB servers
-i--idOrganization ID
--jsonOutput data as JSON (default false)
-n--nameOrganization name
--skip-verifySkip TLS certificate verification
-t--tokenAPI token
--tomlOutput configuration as TOML instead of JSON
--yamlOutput configuration as YAML instead of JSON

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