Stay organized with collections Save and categorize content based on your preferences.
You can use disk metrics to observe your disks' performance and debug performance problems.
Disk metrics can help you answer questions such as the following:
Review your disk's metrics to ensure its performance is sufficient for your workload. In addition, you should also do the following:
Review the disk optimization guidelines. For more information, see Optimize Google Cloud Hyperdisk and Optimize Persistent Disk.
Check the disk's health. For detailed information about disk health, see Monitor disk health.
This document discusses the Persistent Disk metrics Compute Engine automatically collects from each VM and how to view them in Cloud Monitoring, which is Google Cloud's monitoring solution.
Available Persistent Disk metricsYou can view metrics in Cloud Monitoring, or programmatically retrieve Persistent Disk metrics using the REST API, client libraries, Metrics Query Language (MQL), and PromQL.
The following table lists the disk-specific metrics available for every disk. You can collect additional metrics if you install the Ops Agent on your VM.
For a full list of Compute Engine metrics, see Compute Engine metrics.
Each metric type in this table must be prefixed with compute.googleapis.com/
, which has been omitted from the table for readability.
(Metric type)
Description Disk performance statusBETA
(instance/disk/disk_performance_status)
The disk's health over the last minute. This metric indicates if the disk is performing normally or if its performance is affected by an incident within Compute Engine. Possible values are Healthy
, Degraded
, and Severely Degraded
.
(instance/disk/average_io_latency)
The disk's average read/write latency, in microseconds, for the last minute. Average I/O queue depth
(instance/disk/average_io_queue_depth)
The disk's average queue depth for read/write operations over the last minute. Disk read bytes
(instance/disk/read_bytes_count)
Average read throughput, or, the average number of bytes read or written over a period of time specified by the user*. Disk write bytes
(instance/disk/write_bytes_count)
Average write throughput, or, the average number of bytes written over a period of time specified by the user*. Disk read operations
(instance/disk/read_ops_count)
The average number of read operations over a period of time specified by the user*. Disk write operations
(instance/disk/write_ops_count)
The average number of write operations over a period of time specified by the user*. Peak disk read bytes
(instance/disk/max_read_bytes_count)
Peak read throughput, the maximum number of bytes read per second over a period of time specified by the user*. Peak disk write bytes
(instance/disk/max_write_bytes_count)
Peak write throughput, the maximum number of bytes written per second over a period of time specified by the user*. Peak disk read ops
(instance/disk/max_read_ops_count)
The maximum number of read operations per second over a period of time specified by the user*. Peak disk write ops
(instance/disk/max_write_ops_count)
The maximum number of write operations per second over a period of time specified by the user*. Visualize disk performance on a chart
You can visualize your disk's performance by plotting any of the metrics listed in the preceding section with Metrics Explorer. Metrics Explorer is part of Cloud Monitoring.
Example: Visualize average latency for the disks attached to a VMTo visualize the average latency for a VM's disks on a chart, follow these instructions. You can follow the same procedure for the other Persistent Disk metrics.
In the Google Cloud console, go to the leaderboard Metrics explorer page:
If you use the search bar to find this page, then select the result whose subheading is Monitoring.
VM Instance
in the filter bar, and then use the submenus to select a specific resource type and metric:
compute.googleapis.com/instance/disk/average_io_latency
.For more information about configuring a chart, see Select metrics when using Metrics Explorer.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-07 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["Disk metrics allow users to monitor disk performance and identify potential issues, addressing questions about average read IOPS, operation latency, and queue depth."],["Compute Engine automatically collects Persistent Disk metrics, which can be viewed through Cloud Monitoring, REST API, client libraries, Metrics Query Language (MQL), and PromQL."],["A range of disk-specific metrics are available, including performance status, average I/O latency, queue depth, read/write bytes, read/write operations, and peak read/write metrics."],["Users can visualize disk performance using Metrics Explorer within Cloud Monitoring, allowing them to chart metrics like average latency and filter data by instance and device name."],["In addition to monitoring performance metrics, users are also encouraged to review disk optimization guidelines and monitor disk health for comprehensive management."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4