Documentation

influx server-config

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

Flag Description
-c --active-config CLI configuration to use for command
--configs-path Path to influx CLI configurations (default ~/.influxdbv2/configs)
-h --help Help for the list command
--hide-headers Hide table headers (default false)
--host HTTP address of InfluxDB (default http://localhost:8086)
--http-debug Inspect communication with InfluxDB servers
-i --id Organization ID
--json Output data as JSON (default false)
-n --name Organization name
--skip-verify Skip TLS certificate verification
-t --token API token
--toml Output configuration as TOML instead of JSON
--yaml Output configuration as YAML instead of JSON

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: