Available metrics for Hyperdisk pools
This document lists the metrics for Hyperdisk pools, includingHyperdisk Storage Pools and Hyperdisk Exapools.
Metrics help you answer questions about a pool, likeits provisioned performance and capacity, the number of disks in thepool, and its overprovisioning rate.
For instructions on how to view the metrics listed on this page, seeMonitor pool usage and performance.
Before you begin
- If you haven't already, set upauthentication. Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:
Select the tab for how you plan to use the samples on this page:
Console
When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.
gcloud
Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:
gcloudinit
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
Note: If you installed the gcloud CLI previously, make sure you have the latest version by runninggcloud components update.- Set a default region and zone.
REST
To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.
Install the Google Cloud CLI. After installation,initialize the Google Cloud CLI by running the following command:
gcloudinit
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
Note: If you installed the gcloud CLI previously, make sure you have the latest version by runninggcloud components update.For more information, seeAuthenticate for using REST in the Google Cloud authentication documentation.
Hyperdisk pool metrics
The following table lists metrics that are available for both Hyperdisk Storage Poolsand Hyperdisk Exapools.
For metrics specific to Storage Pools andExapools, seeStorage Pool metrics andExapool metrics, respectively.
To refer to the metric programmatically, for example, with PromQL, prefixtheMetric name withcompute.googleapis.com/, which has beenomitted from the table for readability. For example, the fully qualified namefor the capacity overprovisioning metric iscompute.googleapis.com/storage_pool/capacity_overprovisioning.
| Question | Metric | Description |
|---|---|---|
| pool properties | ||
| How many disks are in the pool? | Metric display name: Disks Metric name: ( storage_pool/disks) | The number of disks that are in the pool. |
| How much capacity was provisioned for the storage pool? | Metric display name: Provisioned Capacity Metric name: ( storage_pool/provisioned_capacity) | The size, in TiB, of the pool. |
| Capacity-related metrics | ||
| What percentage of the pool's total capacity has been provisioned to the disks in the pool? (the overprovisioning rate)? | Metric display name: Capacity Overprovisioning (%) Metric name: ( storage_pool/capacity_overprovisioning) | The ratio of the total provisioned capacity of disks in the pool to its provisioned capacity, as a percentage. |
| How much data has been written to the disks in the pool, relative to the pool's provisioned capacity (the utilization rate)? | Metric display name: Capacity Utilization (%) Metric name: ( storage_pool/capacity_utilization) | The used capacity of the pool, represented as a percentage of the overall pool capacity. This value is calculated using the following formula:Utilization = (used_capacity/provisioned_capacity) * 100 |
| How much capacity has been allocated to the disks created in the pool? | Metric display name: Total Disk Provisioned Capacity Metric name: ( storage_pool/total_disk_provisioned_capacity) | The sum of the capacity that is provisioned across all the disks in the pool. For example, a pool with 10 disks, each 5 TiB in size, would return 50 TiB for the Total Disk Provisioned Capacity metric. |
| How much data, in bytes, has been written to the pool, including any data reduction? | Metric display name: Used Capacity Metric name: ( storage_pool/used_capacity) | For Standard capacity pools: This is the sum of the provisioned capacity for all the disks in the storage pool. This is equivalent to Total Disk Provisioned Capacity. For Advanced capacity pools: This is the number of bytes written to the disks in the storage pool. The value is aggregated for all the disks in the storage pool, after data reduction, if supported. |
| Performance-related metrics | ||
| How much throughput has been allocated to the disks created in the storage pool? | Metric display name: Total Provisioned Disk Throughput Metric name: ( /storage_pool/total_provisioned_disk_throughput) | Sum of the provisioned throughput for all the disks in the pool, in MiB/s. |
| How much IOPS has been allocated to the disks created in the storage pool? | Metric display name: Total Provisioned Disk IOPS Metric name: ( /storage_pool/total_provisioned_disk_iops) | Sum of the provisioned IOPS for all the disks in the pool. |
Hyperdisk Storage Pool metrics
The following table lists the metrics available for only Hyperdisk Storage Pools.
| Question | Metric | Description |
|---|---|---|
| Hyperdisk Storage Pool properties | ||
| How much IOPS (read and write) was provisioned for the Storage Pool? | Metric display name: Provisioned IOPS Metric name: ( storage_pool/provisioned_iops) | Provisioned IOPS of the Storage Pool. This metric is only valid for Hyperdisk Balanced Storage Pools. |
| How much throughput (read and write) was provisioned for the Storage Pool? | Metric display name: Provisioned Throughput Metric name: ( storage_pool/provisioned_throughput) | Provisioned throughput of the Storage Pool. |
| Performance usage metrics | ||
| What percentage of the Storage Pool's provisioned IOPS has been provisioned to disks in the pool? | Metric display name: IOPS Overprovisioning (%) Metric name: ( storage_pool/iops_overprovisioning) | The ratio of the total provisioned IOPS of disks in the Storage Pool to its provisioned IOPS, as a percentage. |
| What percentage of the Storage Pool's provisioned throughput has been provisioned to disks? | Metric display name: Throughput Overprovisioning(%) Metric name: ( storage_pool/throughput_overprovisioning) | The ratio of the total provisioned throughput of disks in the Storage Pool to its provisioned throughput, as a percentage. |
| What percentage of the Storage Pool's provisioned IOPS has been consumed by the disks in the pool? | Metric display name: IOPS Utilization (%) Metric name: ( storage_pool/iops_utilization) | Ratio of the total provisioned IOPS of disks in the storage pool to the storage pool provisioned IOPS, as a percentage. |
| What percentage of the pool's total throughput has been consumed by disks? | Metric display name: Throughput Utilization (%) Metric name: ( storage_pool/throughput_utilization) | The used throughput of the Storage Pool, represented as a percentage of its provisioned throughput. This value is calculated using the following formula: Utilization = (used_throughput/provisioned_throughput) * 100 |
| How much of the provisioned IOPS of the pool has been consumed by the disks in the pool? | Metric display name: Used IOPS Metric name: ( storage_pool/used_iops) | The sum of IOPS provisioned for all the disks in the Storage Pool. For Standard performance pools, This is the same as the Total Disk Provisioned IOPS. For Advanced performance pools: This is the sum of the IOPS consumed by all the disks in the Storage Pool for the specified period of time. For Hyperdisk Balanced Storage Pools that use advanced performance provisioning, the first 3,000 IOPS provisioned per disk are not counted towards this value. |
| How much of the provisioned throughput of the pool has been consumed by the disks in the pool? | Metric display name: Used throughput Metric name: ( storage_pool/used_throughput) | The sum of throughput provisioned for all the disks in the storage pool. For Standard performance pools, This is the same as the Total Disk Provisioned Throughput. For Advanced performance pools: This is the sum of the throughput consumed by all the disks in the Storage Pool for the specified period of time. For Hyperdisk Balanced Storage Pools that use advanced performance provisioning, the first 140 MiB/s of provisioned throughput per disk are not counted towards this value. |
Hyperdisk Exapool metrics
The following table lists the metrics available for only Hyperdisk Exapools.
| Question | Metric | Description |
|---|---|---|
| Exapool properties | ||
| How many read IOPS were purchased for the Exapool? | Metric display name: Pool Maximum Read IOPS | The total read IOPS purchased for the Exapool based on the blend of capacity units. |
| How much read throughout was purchased for the Exapool? | Metric display name: Pool Maximum Read Throughput | The total read throughput purchased for the Exapool based on the blend of capacity units. |
| How many write IOPS were purchased for the Exapool? | Metric display name: Pool Maximum Write IOPS | The total write IOPS purchased for the Exapool, based on the blend of capacity units. |
| How much write throughout was purchased for the Exapool? | Metric display name: Pool Maximum Write Throughput | The total write throughput purchased for the Exapool based on the blend of capacity units |
| Performance-related metrics | ||
| How much read IOPS have the disks in the Exapool consumed? | Metric display name: Pool Used Read IOPS Metric name: ( /storage_pool/used_read_iops) | Used read IOPS aggregated for all the disks in the Exapool. You can compare this to the provisioned read IOPS to determine if you need to adjust the blend of capacity units. |
| How much read throughput have the disks in the Exapool consumed? | Metric display name: Pool Used Read Throughput Metric name: ( /storage_pool/used_read_throughput) | Consumed read throughput aggregated for all the disks in the Exapool. |
| How much write IOPS have the disks in the pool consumed? | Metric display name: Pool Used Write IOPS Metric name: ( /storage_pool/used_write_iops) | Used write IOPS aggregated for all the disks in the Exapool. |
| How much write throughput have the disks in the Exapool consumed? | Metric display name: Pool Used Write Throughput Metric name: ( /storage_pool/used_write_throughput) | Used write throughput aggregated for all the disks in the Exapool. |
| Capacity-related metrics | ||
| How much data are workloads writing to the disks in the pool? | Metric display name: Pool User Written Bytes | The sum of the bytes written by application that are using the disks in the Exapool. This field is used to calculate the Data Reduction Ratio metric. It's not used in the Google Cloud console or Google Cloud CLI. |
| How effective are the data reduction strategies? | Metric display name: Pool Data Reduction Ratio | How much data was written by applications on the disks in the pool compared to how much was saved to block storage. It's calculated as:Pool user written bytes / Pool used capacity.For example, a value of "2:1" would mean that every 2 bytes of data that applications write to the disks in the pool is reduced to 1 byte before it's saved to block storage. |
What's next
To learn how to review a pool's metrics, seeMonitor pool usage and performance.
For a full list of all disk metrics, seeCompute Engine metrics.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-18 UTC.