Documentation

Get cluster information

Use the Admin UI or the influxctl cluster get CLI command to view information about your InfluxDB Cloud Dedicated cluster, including:

  • Cluster ID
  • Cluster name
  • Cluster URL
  • Cluster status
  • Cluster size (standard or custom)

Access the Cloud Dedicated Admin UI

  1. To access the InfluxDB Cloud Dedicated Admin UI, visit the following URL in your browser:

    https://console.influxdata.com
    
  2. Use the credentials provided by InfluxData to log into the Admin UI. If you don’t have login credentials, contact InfluxData support.

    After you log in, the Account Management portal displays account information and lists all clusters associated with your account.

  3. Search for the cluster or use the sort button and column headers to sort the cluster list and find the cluster.

View cluster details

The cluster list displays the following cluster details:

  • Cluster ID and name
  • Status (ready, provisioning, etc.)
  • Size (standard or custom)
  • URL endpoint

Cluster management tools

The options button (3 vertical dots) to the right of any cluster provides additional tools for cluster management:

  • Copy Cluster ID
  • Copy Cluster URL
  • Observe in Grafana (only if your cluster has enabled operational dashboards. For more information, see how to monitor your cluster.)
  1. If you haven’t already, download and install the influxctl CLI, and then configure a connection profile for your cluster.

  2. Run influxctl cluster get with the following:

influxctl cluster get --format table 
CLUSTER_ID

Replace CLUSTER_ID with the ID of the cluster you want to view information about.

Output formats

The influxctl cluster get command supports two output formats: table and json. By default, the output is formatted as a table. For additional cluster details and easier programmatic access to the command output, include --format json with your command to format the cluster as a JSON object.

Example output

+-------+----------------------------------------------------+
|    id | X0x0xxx0-0XXx-000x-00x0-0X000Xx00000                |
|  name | Internal - Cluster 1                               |
| state | ready                                              |
|   url | X0x0xxx0-0XXx-000x-00x0-0X000Xx00000.a.influxdb.io  |
+-------+----------------------------------------------------+

Detailed output in JSON

For additional cluster details and easier programmatic access to the command output, include --format json with your command–for example:

influxctl cluster get --format json X0x0xxx0-0XXx-000x-00x0-0X000Xx00000

The output is the cluster as a JSON object that includes additional fields such as account ID and created date.

{
    "account_id": "0x0x0x00-0Xx0-00x0-x0X0-00x00XX0Xx0X",
    "cluster_id": "X0x0xxx0-0XXx-000x-00x0-0X000Xx00000",
    "name": "Internal - Cluster 1",
    "url": "X0x0xxx0-0XXx-000x-00x0-0X000Xx00000.a.influxdb.io",
    "state": "ready",
    "created_at": {
      "seconds": 1686670941,
      "nanos": 520023000
    },
    "category": 1
}

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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