> For the complete documentation index, see [llms.txt](https://ai-docs.fptcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-virtual-machine/on-fpt-cloud-console/tutorials/monitoring-gpu-vms.md).

# Monitoring GPU VMs

GPU Virtual Machine provides metrics to help you monitor and troubleshoot your workloads. Monitoring metrics are collected to track the performance, availability, and resource usage of services, helping detect issues and optimize operations. Note that metric data is retained for **30 days**.

There are 3 metric groups:

* **Utilization metrics**: Monitor CPU, memory, and GPU usage to assess system performance and resource efficiency.
* **Disk metrics**: Track disk read/write speed, and latency to detect storage issues or bottlenecks.
* **Network metrics**: Measures the amount of data read/written and shows how frequently those read/write actions occur.

For additional metrics, please contact us to explore our advanced monitoring service.

<figure><img src="https://2158065032-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2FDB5fvsiFxYI972UDTv%2Fuploads%2FWIcLzsTIDnhCxKoaA9Wg%2Fimage.png?alt=media&amp;token=95416e02-f3c8-44f1-b193-cf7435bf592a" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-virtual-machine/on-fpt-cloud-console/tutorials/monitoring-gpu-vms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.