Documentation

influxctl cluster get

The influxctl cluster get command returns information about an InfluxDB cluster.

The --format flag lets you print the output in other formats. The json format is available for programmatic parsing by other tooling. Default: table.

Usage

influxctl cluster get <CLUSTER_ID>

Arguments

ArgumentDescription
CLUSTER_IDID of the cluster to get

Flags

FlagDescription
--formatOutput format (table (default) or json)
-h--helpOutput command help

Examples

Return information about a cluster
influxctl cluster get 000xX0Xx-00xX-XXx0-x00X-00xxX0xXX00x

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