# HI GIO's Monitoring Alert - Email notification channel
## **Overview**
This function is designed to enable users to create rules for receiving notifications if the statuses of VMs exceed or fall below specific thresholds. The resources that can be monitored and notified are:
*- CPU Usage.*
*- Memory Usage.*
*- Free Disk Space.*
## **Procedure**
{% tabs %}
{% tab title="I. Creating Alert Contact Destination" %}
The recipients will receive notifications when the alert is triggered.
* Log in to HI GIO cloud > **Monitor**
* Select **Manage**, and Select **NEW** below the *Alert Contact Destination* section.
* A new Alert Contact Destination will open. Fill up contact information to this window> **SAVE**
\*\* Please add to the email whitelist.
{% hint style="warning" %}
#### *Requirement fields explanation:*
**Name**: The name of the contact destination.
**Integration**: The channel where users can receive alerts. In this version, there is only 1 channel available: Email.
**Email Address:**
* The email address of the persons who will receive the alert email.
* We can add multiple email addresses but only add 1 email at a time. After inputting a correct email address and pressing the Enter key, the email address will be added to the text area below, and then we can add another one.
**Email Subject:** The alert email’s subject.
**Send a single email to all recipients** check box:
* If checked, 1 email will be sent to all recipients. All recipients will be displayed in “To“ field.
* If not checked, each recipient will receive a separate email >> We don’t know who gets the notify email.
{% endhint %}
{% endtab %}
{% tab title="II. Creating Alert rule" %}
An alert rule is a configuration that defines conditions under which an alert should be triggered.
* Log in to HI GIO cloud > **Monitor**
* Select **Manage**, and Select **NEW** below the *Alert Rules* section.
* New Alert Rule window will open. Fill up the information in this window> **SAVE**
{% hint style="warning" %}
#### *Requirement fields explanation:*
**Name**: The name of the rule.
**Item**: The resource that triggers the alert. For example, CPU.
**Threshold**: Specify specific values or ranges that activate the alert. For example, 90% (meaning that if CPU usage exceeds 90%, the alert will be triggered).
**oVDC**: Specify the oVDC.
**VM**: Specify the VM that triggers the alert. The select box will contain all VMs in the oVDC and **/.\*/** option indicates the selection of all VMs.
**Pending Period:**
* The duration for which an alert remains pending after being triggered.
* During this pending period, Grafana allows time for conditions to potentially resolve on their own before considering the alert fully triggered or resolved.
* This feature helps avoid unnecessary alert notifications for transient issues.
* The default value is 3m.
*For example,* Pending Period = 3m → means that if the CPU exceeds 90%, the system will wait 3 minutes. Within 03 minutes, if the CPU falls behind 90%, no alert will be fired. The alert will only be fired if the CPU exceeds 90% after a 3-minute.
**Repeat Interval:**
* It specifies how frequently the system checks whether the conditions for triggering the alert are still met after the initial alert firing.
* If the conditions remain true during these intervals, the system continues to send notifications at the specified repeat interval until the alert condition is no longer met or resolved.
* For example, Repeat Interval = 4h and the condition is CPU exceeds 90% → meaning that after an alert is first fired, the system will continue to fire the alert every 4 hours as long as the CPU still exceeds 90%.
**Annotation** – Summary, Description: The alert email’s content.
**Alert Contact Destination:** The destination where the alert will be sent. The select box contains all the created contact destinations.
{% endhint %}
* After it is completed, the alert rule will show as below:
We also can activate\deactivate the rules directly from this list.
{% hint style="warning" %}
Update the VM field If you rename the VM’s name on the porta
**Alert Rule** will not automatically update the VM’s name on the VM field.
{% endhint %}
{% endtab %}
{% tab title="III. Notification Emails" %}
Every threshold reaches the defined in the alert rule. we will get the email notification - **Firing Instance**\\**Resolved Instances**.
Sample email - Firing Instance.
Sample email - Resolved Instances.
{% endtab %}
{% endtabs %}
---
# Agent Instructions: 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:
```
GET https://docs.higiocloud.vn/management/1.-iam-portal/hi-gios-monitoring-alert-email-notification-channel.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.