...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
This function is designed to enable users to create the 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.
...
I. Creating Alert Contact Destination: The recipients for whom will receive notifications when the alert is triggered.
...
| Expand |
|---|
Log in to HI GIO cloud > Monitor Select Manage, and Select NEW below the Alert Contact Destination section.
|
...
 Image Added |
...
...
...
 Image Added |
info| Note |
|---|
Requirement fields explanation:Name: The name of the contact destination. Integration: The channel |
that where users can receive alerts. In this version, there is only 1 channel available: Email. Email Address: |
, we can mail’s 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 get the notify email.
|
|
II. Creating Alert rule: An alert rule is a configuration that defines conditions under which an alert should be triggered.
...
...
 Image Added |
...
...
 Image Modified |
...
| Note |
|---|
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 in a pending state 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 |
|
...
...
...
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 |
|
...
...
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. |
|
...
 Image AddedWe also can activate\deactivate the rules directly from this list. | Note |
|---|
Update the VM field If you rename the VM’s name on the portal. Alert Rule will not automatically update the VM’s name |
automatically |
III. Notification Emails:
| Expand |
|---|
Every threshold reaches the |
...
defined in the alert rule. we will get the email |
...
notification - Firing Instance\Resolved Instances.  Image Modified Image Modified
End. |