Documentation

influxdb3 CLI

The influxdb3 CLI runs and interacts with the InfluxDB 3 Enterprise server.

Usage

influxdb3 [GLOBAL-OPTIONS] [COMMAND]

Commands

CommandDescription
createCreate resources
deleteDelete resources
disableDisable resources
enableEnable resources
queryQuery InfluxDB 3 Enterprise
serveRun the InfluxDB 3 Enterprise server
showList resources
testTest plugins
updateUpdate resources
writeWrite to InfluxDB 3 Enterprise

Global options

OptionDescription
-h--helpPrint help information
--help-allPrint detailed help information including runtime configuration options
-V--versionPrint version

For advanced global configuration options (including --num-io-threads and other runtime settings), see Configuration options.

Quick-Start Mode

For development, testing, and home use, you can start InfluxDB 3 Enterprise by running influxdb3 without the serve subcommand or any configuration parameters. The system automatically generates required values:

  • node-id: {hostname}-node (fallback: primary-node)
  • cluster-id: {hostname}-cluster (fallback: primary-cluster)
  • object-store: file
  • data-dir: ~/.influxdb

The system displays warning messages showing the auto-generated identifiers:

Using auto-generated node id: mylaptop-node. For production deployments, explicitly set --node-id
Using auto-generated cluster id: mylaptop-cluster. For production deployments, explicitly set --cluster-id

Production deployments

Quick-start mode is designed for development and testing environments. For production deployments, use explicit configuration with the serve subcommand and specify all required parameters as shown in the Examples below.

Configuration precedence: CLI flags > environment variables > auto-generated defaults

For more information about quick-start mode, see Get started.

Examples

In the examples below, replace the following:

  • my-host-01: a unique identifier for your InfluxDB 3 Enterprise server.
  • my-cluster-01: a unique identifier for your InfluxDB 3 Enterprise cluster. The value you use must be different from --node-id values in the cluster.

Quick-start influxdb3 server

# Zero-config startup
influxdb3

# Override specific defaults
influxdb3 --object-store memory

# Use environment variables to override defaults
INFLUXDB3_NODE_IDENTIFIER_PREFIX=my-node influxdb3

Run the InfluxDB 3 server

influxdb3 serve \
  --object-store file \
  --data-dir ~/.influxdb3 \
  --node-id 
my-host-01
\
--cluster-id
my-cluster-01

Run the InfluxDB 3 server with custom IO threads

influxdb3 --num-io-threads=8 serve \
  --object-store file \
  --data-dir ~/.influxdb3 \
  --node-id 
my-host-01
\
--cluster-id
my-cluster-01

Display short-form help for all commands

influxdb3 -h

Display long-form help for all commands

influxdb3 --help

Run the InfluxDB 3 Enterprise server with extra verbose logging

influxdb3 serve \
  --object-store file \
  --data-dir ~/.influxdb3 \
  --node-id 
my-host-01
\
--cluster-id
my-cluster-01
\
--verbose

Run InfluxDB 3 Enterprise with debug logging using LOG_FILTER

LOG_FILTER=debug influxdb3 serve \
  --object-store file \
  --data-dir ~/.influxdb3 \
  --node-id 
my-host-01
\
--cluster-id
my-cluster-01

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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