> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/welcome/cn/elastic-compute/instance-monitoring/05-disk.md).

# 我的磁盘表现如何？

所有磁盘面板的范围限定于单个挂载卷——请从该部分顶部的下拉菜单中选择卷。

## Throughput — Read / Write

Guest 向存储层请求的每秒字节数，在块设备的宿主机侧进行测量。这是与 Guest 上报内容无关的真实视图。

## Operations (IOPS) — Read / Write

每秒读写请求数。结合 Throughput 一起阅读，可计算平均请求大小——小块随机 I/O 与大块顺序 I/O 的行为差异极大，应分开分析。

## Disk Utilization

块设备的繁忙程度，由累计服务时间计数器推导而来。该面板用于区分"我的磁盘很慢"和"我的磁盘很忙"：

* **高利用率伴随高 IOPS** — 工作负载正在使其磁盘层饱和。请降低请求速率、批量写入，或升级磁盘层级。
* **高利用率伴随低 IOPS** — 请求速率不高，但每个请求响应很慢。这指向存储后端问题；请联系支持。

## API 参考

所有磁盘指标均使用 `DescribeDiskMonitorData`，并配合以下 `metricType` 值。

| Console 面板                | metricType         |
| ------------------------- | ------------------ |
| Throughput — Read         | `DISK_READ_BYTES`  |
| Throughput — Write        | `DISK_WRITE_BYTES` |
| Operations (IOPS) — Read  | `DISK_READ_OPS`    |
| Operations (IOPS) — Write | `DISK_WRITE_OPS`   |
| Disk Utilization          | `DISK_UTIL`        |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.console.zenlayer.com/welcome/cn/elastic-compute/instance-monitoring/05-disk.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.