How to view cluster resources

When to use

Before placing new virtual machines, expanding a virtual data center (VDC), or decommissioning a node, you need to understand the cluster's available capacity. vStack Center displays this capacity in three views that answer different questions. Aggregate metrics show how much capacity remains in total. The breakdown by node shows which node is closest to its limit. Cluster membership shows what the cluster contains and what is running.

Distinguish between three quantities. Capacity is the amount of hardware physically available. Provisioned resources are those allocated to virtual machines. Consumption is the amount actually used. Provisioning can exceed actual consumption several times over — this is how overcommitment works.

Question	Where to view	What is visible
How much cluster capacity is available and how much is used	Provider Data Center → Overview screen	CPU, memory, and storage totals
Which node is closest to its limit	Overview, Resources tab, and Server Nodes table	Provisioning and consumption by node
What the cluster contains and what is running	Server Nodes and Storage Resources	Nodes and pools with their statuses

Prerequisites

The Cluster master (role_id=1) or Resource viewer (role_id=5) role — the cluster resource overview is available only to these roles;
The View Cluster Status Map (full) (6003) or View Cluster Status Map (dashboard) (6004) privilege — to view cluster membership and statuses;
Metrics collected in InfluxDB, if you need actual consumption values;
vStack Center version 3.0.3.

Step 1. Cluster totals

Start with the overall picture.

Open Provider Data Center and select a cluster.
Go to the Overview screen.

The screen brings together capacity, provisioning, and actual consumption for three resource types.

Resource	Capacity	Provisioned	Consumption
CPU	Cores on all cluster nodes	Cores allocated to running VMs	Actual core utilization, from InfluxDB
Memory	Memory on all nodes	Memory of running VMs	Memory actually used, from InfluxDB
Storage	Total pool capacity	Requested volume capacity	Space used in pools

Do not confuse provisioning with consumption: the former is the cluster's commitment, the latter is actual usage. Use provisioning to decide whether another machine will fit.

Step 2. Breakdown by node and pool

Totals can hide an imbalance: the cluster may have spare capacity overall while a specific node can no longer accept new machines.

On the Overview screen, open the Resources tab. The table shows cluster nodes with the Node name, Node health, and Consuming columns — the share of consumption for each node.
For a row-by-row view, open Server Nodes. The node table has ID, Name, Health, CPU (Cores), and RAM (GB) columns; next to it are the CSV button for exporting the table and the Software button for package versions.
View pools in Storage Resources. The ZFS pools table has GUID, Name, Health, Consuming, Scrubbing, Resilvering, Current node, and Capacity (RAW) columns.

Points to interpret correctly:

Provisioning percentages are calculated from node capacity, accounting for its reserve; a value greater than 100 indicates overcommitment;
Remaining node memory is calculated from allocated memory rather than memory actually used;
For a pool, Consuming concerns consumption and Capacity (RAW) concerns raw capacity; these are different quantities and do not have to match;
Current node identifies the node currently hosting the pool; the value changes after the pool is moved.

A node without metrics is a typical case: the CPU (Cores) and RAM (GB) columns are empty, and consumption is zero. Provisioned values remain reliable.

Step 3. Cluster membership and statuses

Capacity does not tell you whether everything is running. Cluster membership does.

Open Server Nodes: the Health column shows each node's state, and the tabs below the table (node01, node02, and so on) open the node cards.
Open Storage Resources: the Health column shows pool state, Current node shows the node hosting the pool, and Scrubbing and Resilvering show whether pool integrity checks and rebuilding are in progress.
If a node is shown as running but has been taken out of service by an administrator, look for the difference in the node's status pair — its structure is described in Cluster, nodes, and services.

Alongside nodes and pools, vStack Center displays the state of the management machine. It hosts the control plane and is not part of the cluster, so interpret its state separately from node state.

Verify the result

Compare the views. All nodes visible in Server Nodes must also appear in the table on the Resources tab. A node shown as running has values in the CPU (Cores) and RAM (GB) columns. Empty values for a running node indicate missing metrics.

Troubleshooting

What you see	Why	What to do
The resource overview does not open, error code `-403`	The role does not have access to the cluster overview	Sign in with a cluster-level role
Error code -15905 or -15925	The InfluxDB metrics store did not respond	Check metrics store availability; provisioned values on the screen remain reliable
Error code -15903 or -15923	HTTP error when accessing the metrics store	Same action; the failure is in the metrics system, not the cluster
Error code -15904 or -15924	Unknown metrics store error	Reopen the screen; if the error recurs, check the log
Error code -7	Database error	Reopen the screen; if the error recurs, troubleshoot the control plane
The node list is not displayed, error code -10	Node status was not retrieved from Cluster Manager	Check Cluster Manager availability: there is no source to read cluster membership from
The service list is not displayed, error code -11	Service status was not retrieved from Cluster Manager	Same action
The CPU (Cores) and RAM (GB) columns are empty, consumption is zero	The metrics store has no data for the node	Use provisioned values; restore metrics collection
The node's pools are missing from Storage Resources	There is no pool data for the node	Check pool state separately; the node may have been taken out of service
Only the VDC list is visible, with no cluster membership data	The user does not have privilege 6003 or 6004	Request the privilege to view the status map

API methods

API operations covered on this page: cluster-totals, cluster-overview, get-statusmap — see the API reference.

When to use​

Prerequisites​

Step 1. Cluster totals​

Step 2. Breakdown by node and pool​

Step 3. Cluster membership and statuses​

Verify the result​

Troubleshooting​

See also​

API methods​