Documentation

influxdb3 show nodes

The influxdb3 show nodes command displays information about nodes in your InfluxDB 3 Enterprise cluster, including their state, mode, and resource usage.

Usage

# Syntax
influxdb3 show nodes [OPTIONS]

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Enterprise server (default is http://127.0.0.1:8181)
--formatOutput format (pretty (default), json, jsonl, csv, or parquet)
--outputPath where to save output when using the parquet format
--tokenAuthentication token
--tls-caPath to a custom TLS certificate authority (for testing or self-signed certificates)
--tls-no-verifyDisable TLS certificate verification (Not recommended in production, useful for self-signed certificates)
-h--helpPrint help information

Option environment variables

You can use the following environment variables to set command options:

Environment VariableOption
INFLUXDB3_HOST_URL--host
INFLUXDB3_AUTH_TOKEN--token
INFLUXDB3_TLS_NO_VERIFY--tls-no-verify

Output

The command displays the following information for each node:

  • node_id: The unique identifier for the node
  • node_catalog_id: The internal catalog identifier
  • instance_id: The unique instance identifier
  • mode: The node’s operating modes (ingest, query, process, compact)
  • core_count: Number of CPU cores allocated to the node
  • state: Current node state (running or stopped)
  • updated_at: Timestamp of the last update
  • cli_params: Command-line parameters used to start the node

Examples

List all nodes in pretty format

influxdb3 show nodes
+----------+-----------------+--------------------------------------+--------+------------+---------+---------------------------+
| node_id  | node_catalog_id | instance_id                          | mode   | core_count | state   | updated_at                |
+----------+-----------------+--------------------------------------+--------+------------+---------+---------------------------+
| node-1   | 0               | e38944e4-1204-4bb4-92f3-71138894d674 | ingest | 1          | running | 2025-09-04T10:15:57.126   |
| node-2   | 1               | f5418c97-eb6d-47b5-8176-efc0ad7b882e | ingest | 1          | stopped | 2025-09-04T10:16:57.503   |
+----------+-----------------+--------------------------------------+--------+------------+---------+---------------------------+

List nodes in JSON format

influxdb3 show nodes --format json

The output is similar to the following:

[
  {
    "node_id": "node-1",
    "node_catalog_id": 0,
    "instance_id": "e38944e4-1204-4bb4-92f3-71138894d674",
    "mode": [
      "ingest"
    ],
    "core_count": 1,
    "state": "running",
    "updated_at": "2025-09-04T10:15:57.126",
    "cli_params": "{\"http-bind\":\"127.0.0.1:8181\",\"node-id\":\"node-1\",\"data-dir\":\"/path/to/data\",\"object-store\":\"file\",\"mode\":\"ingest\"}"
  },
  {
    "node_id": "node-2",
    "node_catalog_id": 1,
    "instance_id": "f5418c97-eb6d-47b5-8176-efc0ad7b882e",
    "mode": [
      "ingest"
    ],
    "core_count": 1,
    "state": "stopped",
    "updated_at": "2025-09-04T10:16:57.503",
    "cli_params": "{\"http-bind\":\"127.0.0.1:8182\",\"node-id\":\"node-2\",\"data-dir\":\"/path/to/data\",\"object-store\":\"file\",\"mode\":\"ingest\"}"
  }
]

Export nodes data to Parquet format

Parquet is a binary format. Use the --output option to specify the file where you want to save the Parquet data.

influxdb3 show nodes \
  --format parquet \
  --output nodes-data.parquet

List nodes on a remote server

influxdb3 show nodes \
  --host 
INFLUXDB_HOST
\
--token
AUTH_TOKEN

Replace the following:

  • AUTH_TOKEN: Authentication token with sufficient privileges
  • INFLUXDB_HOST: Host URL of the running InfluxDB 3 Enterprise server

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