Load Alerts
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use Load Alerts on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
When you create an environment in the platform, it is necessary to set cloudlet limits for each node to control costs by limiting resource usage. However, as traffic increases, Applications may request additional resources to function efficiently. If the set limit is too low It may cause system performance to deteriorate or the application to fail to provide service.
To be able to track the operating status of the application including loading and resource usage closely Users can set up automatic alerts (Automatic Alerts). The system will notify them when the usage of certain types of resources exceeds or falls below the specified values. (in the form of percentage %) within the specified period
With this notification setting Users will receiveNotification emailregarding timely changes in application load It allows for efficient management and optimization of resources.
- wp:list-item
- Create a notification
- Operation history /wp:list-item
Creating a notification
You can set up alerts to monitor your Environment's resource usage by following these steps:
1. Open the settings for Environment. Click the button.Settingsfor the desired environment
2. Go to the tabLoad Alerts
If the hosting provider has predetermined You'll see a list of default triggers that are automatically generated, such as RAM, CPU, Disk, Inodes, or Network Traffic usage approaching limits. There will be an automatic notification.
3. Manage notification list
- wp:list-item
- Use the buttons on the toolbar to:wp:list wp:list-item
- Add: Add new trigger. /wp:list-item wp:list-item
- Edit: Edit an existing item. /wp:list-item wp:list-item
- Remove: Delete trigger. /wp:list-item wp:list-item
- Enable/Disable: Enable/Disable trigger. /wp:list-item wp:list-item
- Refresh: Reload the list again. /wp:list-item /wp:list /wp:list-item
It is recommended to check the default trigger first. And consider setting up additional triggers to suit your usage.
Let's consider your trigger settings - button clicks.AddAbove as pictured
4. Adding notificationsAdd alertSet the following values:
- wp:list-item
- Name- Name of the notification trigger. /wp:list-item wp:list-item
- Nodes- Type of node to be inspected. (You can select either a single node or multiple nodes within the same environment) /wp:list-item wp:list-item
- Whenever- Type of resource to monitor, such as: Cloudlets (Memory, CPU), Memory, CPU, Network (out ext. + in ext.), Network (out ext.), Storage (disk space amount), Disk I/O, Disk IOPS and Inodes. /wp:list-item wp:list-item
- Is- Trigger condition: When resource usage is “greater than” or “less than” the configured value. (Specified as a percentage or Mbps for Network) /wp:list-item wp:list-item
- For at least- How long the condition must be true before the system will process the notification. /wp:list-item wp:list-item
- Notification frequency- Frequency of repeated notifications If the condition remains true
After you have completed all the desired values, click the button.Add
5. When notifications are configured and enabled, the values specified in the previous step will appear in the list.
6. When resource usage is higher or lower than the specified value. (according to the conditions set in the trigger) within the specified time period. The system will sendAutomatic email notificationsIt includes the following information:
- wp:list-item
- Current resource usage value(Current usage level) /wp:list-item wp:list-item
- Advice on problemsor what should be done to correct the situation /wp:list-item wp:list-item
- Link for adjusting Node limit size(so that additional resources can be quickly allocated) /wp:list-item
With this notification system Administrators can respond to problems resulting from over or under resource use in a timely manner. Helps prevent application interruptions and maintain service efficiency.
Note:If the Environment is shared with other users (via theSharedenvironment) Users with access rights will receive Email notifications about system load Same as Environment owner
Alert trigger history
You can check the history of Load Alerts triggers for nodes within a given Environment by following the steps below:
1. Go to the menuHistoryWithin the Settings of the Environment
2. Select the Node and time period you want to view.
3. You will see a list of notifications that were enabled during the specified time period and contain information about:
- wp:list-item
- DateThe date and time the trigger was run. /wp:list-item wp:list-item
- NameName of the enabled notification trigger. /wp:list-item wp:list-item
- NodesType of node used for checking alarm conditions. /wp:list-item wp:list-item
- ConditionCondition that triggers the alert (e.g. Cloudlet > 60%) /wp:list-item wp:list-item
- ResultNotification results (e.g., whether the notification was sent successfully or failed)
4. Click the specific load alert you want to view details on the right. Contains the following information:
- wp:list-item
- Loading Value- Resource usage level at the time the trigger was executed (the number of Cloudlets used is indicated in parentheses). /wp:list-item wp:list-item
- Action- The action the system takes after the trigger is fired (such as sending a notification email).
with this tool You can trace back when an application's load was unusually high or low. And has there been any notification action? This allows you to analyze resource usage trends and customize trigger settings with more precision.