Versions Compared

Old Version 2

changes.mady.by.user Tran Dai Quan

Saved on

compared with

New Version 3

changes.mady.by.user Tran Dai Quan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

INTRODUCTION

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: 

...

- Memory Usage. 

- Free Disk Space. 

PROCEDURE:

I. Creating Alert Contact Destination: The recipients for whom will receive notifications when the alert is triggered.  

...

New Alert Contact Destination will open. Fill up contact information to this windows > SAVE

 

...

Please add no-reply-iam@higiocloud.vn to email whitelist.

Info

Requirement fields explanation:

Name: The name of the contact destination. 

Integration: The channel that 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 we can only add 1 email at a time. After inputting a correct email address and pressing Enter key, the email address will be added to the text area below, and then we can add another one. 

Email Subject: The alert mail’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. 

...

New Alert Rule window will open. Fill up the information to this windows > SAVE

...

Info

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 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: Pending Period = 3m → meaning that if CPU exceeded 90%, the system will wait for 3 minutes. Within 03 minutes, if the CPU falls back behind 90%, no alert be fired. The alert will only be fired if CPU still exceeds 90% after 3-minutes period. 

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 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 mail’s content. 

Alert Contact Destination: The destination where the alert will be sent. The select box contains all the created contact destinations. 

...

We also can activate\deactivate the rules directly from this list. 

IIII. Notification Emails:

Every the threshold reach to defined in alert rule. we will get the email notify - Firing Instance\Resolved Instances.

...