> For the complete documentation index, see [llms.txt](https://docs.higiocloud.vn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.higiocloud.vn/management/1.-iam-portal/hi-gios-vm-monitoring.md).

# HI GIO's VM monitoring

## <mark style="color:green;">**Overview**</mark> <a href="#overview" id="overview"></a>

This function aims to provide tenant users/service providers a visual look at the status of each VM based on its metrics:

*o   **CPU** Usage.*

*o   **Memory** Usage.*

*o   **Disk** used Space.*

*o   **Disk** Average number of bytes read.*

*o   **Disk** Average number of bytes written.*

*o   **Network** utilization on interfaces.*

In this guide, we will help you:

* How to enable Monitor Zones
* How to view monitor items on your organization.

## <mark style="color:green;">**Procedure**</mark> <a href="#procedure" id="procedure"></a>

{% stepper %}
{% step %}
**Step 1:  Enable Monitor Zones**

This page lists out all managed regions of your account and lets you enable monitoring for them.

Log on to the IAM portal. Select **Monitor > Manage**

Select *Zone* > Change to **Active**

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2FtH5LwfpmPVb6nJKFLdew%2Fimage.png?alt=media&amp;token=d39f7c87-18db-4e26-8103-bd669a27a9a2" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Step 2: View monitor items on your organization:**

Log on IAM portal. Select **Monitor > View.**

In Monitor View window, you can select: IaaS Zone *\[3]*, oVDC *\[4]* which one you want to view.

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2FtuTPaoxhPErL3GQKNHFV%2Fimage.png?alt=media&amp;token=f72a0891-42a0-4d93-b3a3-7c7b97c6055d" alt=""><figcaption></figcaption></figure>

Select **VM name** from list *\[5]* to open monitor items of VMs.

On this page, you can select:

*<mark style="color:blue;">\[1]</mark>* <mark style="color:blue;"></mark><mark style="color:blue;">oVDC</mark>

*<mark style="color:blue;">\[2]</mark>* <mark style="color:blue;"></mark><mark style="color:blue;">VM</mark>

*<mark style="color:blue;">\[3]</mark>* <mark style="color:blue;"></mark><mark style="color:blue;">Network (if VM have multiple NIC)</mark>

*<mark style="color:blue;">\[4]</mark>* <mark style="color:blue;"></mark><mark style="color:blue;">Disk (if VM have multiple disk)</mark>

<figure><img src="https://3953927389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbvay7AR0CH8vZKgD3dSy%2Fuploads%2Fj2Zb3ZEHjqjvrcKwVUXz%2Fimage.png?alt=media&amp;token=7cd3e8ef-cc20-408b-ad72-6d34e52a9621" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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://docs.higiocloud.vn/management/1.-iam-portal/hi-gios-vm-monitoring.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.