Load Alerts

Load Alerts

Load alerts help you monitor resource consumption and receive notifications when a selected environment layer exceeds or falls below a defined threshold. They can be used to detect performance problems before they affect application availability.

In this article

Load Alert Overview

A load alert continuously evaluates a selected monitoring condition for an environment layer or node group. When the configured condition remains true for the required period, the platform generates an alert and sends a notification through the available notification channels.

Resource monitoringTracks selected performance indicators such as processor, memory, network or storage activity.
Threshold conditionsTriggers an alert when resource usage rises above or drops below the defined value.
Duration controlRequires the condition to remain active for a selected period before notifying the user.
Layer-level monitoringApplies the alert to the selected environment layer or node group.
✓

Use alerts together with automatic scaling

Load alerts notify administrators about abnormal resource usage, while automatic scaling can add or remove resources according to predefined conditions.

Open the Load Alert Settings

1

Open the environment

Locate the required environment in the dashboard.

2

Open environment settings

Click the environment settings or configuration icon.

3

Select Monitoring

Open the monitoring section and select Load Alerts.

Load alerts settings in the environment dashboard
Open the Load Alerts section from the environment settings.

Create a Load Alert

1

Click Add

Use the add control to create a new alert rule.

2

Select the environment layer

Choose the node group or container layer that must be monitored.

3

Select the monitored metric

Choose the resource or performance indicator that will be evaluated.

4

Define the comparison condition

Select whether the alert should activate when the value is above or below the specified threshold.

5

Enter the threshold and duration

Specify the resource value and how long the condition must remain active before the alert is triggered.

6

Save the alert

Review the configuration and confirm the new rule.

Create a new load alert rule
Select the layer, metric, condition, threshold and duration.
!

Avoid very short alert durations

Temporary resource spikes are common. Use a suitable duration so that the alert identifies sustained load rather than brief normal activity.

Available Monitoring Conditions

The exact list of available metrics depends on the node type and platform configuration. Common alert conditions may include the following resource indicators.

Metric What it indicates Typical reason for monitoring
CPU usage The percentage of processor capacity currently used by the selected layer. Detect sustained processing load or insufficient compute resources.
Memory usage The amount or percentage of available RAM being consumed. Identify memory pressure, leaks or insufficient memory allocation.
Network traffic The amount of inbound or outbound data transferred by the nodes. Detect unusual traffic levels or capacity requirements.
Disk activity The read, write or input/output load generated by the application. Identify storage bottlenecks or unexpectedly intensive operations.
Disk space The amount of storage capacity that is used or remains available. Prevent application failures caused by insufficient free storage.
i

Metric names may differ

The names, measurement units and available conditions displayed in the dashboard can vary according to the hosting provider, node type and platform version.

Configure Alert Notifications

When the rule condition is met, the platform records the event and sends a notification through the channels enabled for the account. Depending on the platform configuration, this may include dashboard notifications, email messages or other integrated notification methods.

Alert activationA notification is generated after the selected threshold condition remains true for the configured duration.
Alert recoveryA follow-up notification may be generated when the monitored value returns to the normal range.
Account recipientsNotifications are delivered according to the email address and notification settings configured for the account.
Dashboard recordThe environment event and alert status can be reviewed from the platform interface.
Load alert notification example
A load alert notification identifies the affected environment, layer and monitored condition.

Edit, Disable or Remove an Alert

Existing alert rules are listed in the Load Alerts section. Use the available controls to update a rule, temporarily disable monitoring or permanently remove the alert.

EditChanges the monitored layer, metric, threshold, comparison condition or duration.
Enable or disableTemporarily activates or pauses the rule without deleting its configuration.
RemovePermanently deletes the alert rule from the environment.
✓

Review alerts after topology changes

When layers are added, removed or renamed, verify that all alert rules still monitor the correct application components.

Configuration Recommendations

  • Set thresholds according to the normal usage pattern of the application.
  • Use a duration that filters out short, harmless load spikes.
  • Create separate alerts for critical processor, memory, storage and traffic conditions.
  • Use lower thresholds for services where early notification is important.
  • Check that the account email address and notification preferences are current.
  • Review alert history together with monitoring graphs before increasing resources.
  • Update or remove obsolete rules after changing the environment topology.
  • Combine alerts with scaling rules where automatic resource adjustment is required.

Expected Result

The platform monitors the selected environment layer using the configured metric, threshold and duration. When the condition is met, an alert is recorded and the configured account recipients are notified so that corrective action can be taken.

Important Notes

  • A load alert provides notification but does not automatically resolve the underlying resource problem.
  • Brief resource spikes may not indicate a fault and should be filtered using an appropriate duration.
  • The available monitoring metrics depend on the selected node type.
  • Alert thresholds should be reviewed whenever application load or resource limits change.
  • Notification delivery depends on valid account contact information and enabled notification settings.
  • Use monitoring graphs and application logs to investigate the cause of an alert.

Common Issues and Solutions

No notification is receivedCheck the account email address, notification settings and spam folder, and confirm that the rule is enabled.
Alerts are triggered too frequentlyIncrease the threshold or require the condition to remain active for a longer duration.
An expected alert is not triggeredVerify the selected layer, comparison operator, threshold, measurement unit and duration.
The wrong node group is monitoredEdit the alert and select the correct environment layer.
Resource usage remains high after the alertReview monitoring charts, logs and application activity, then scale resources or optimize the application.
An obsolete alert remains activeDisable or remove the rule after confirming that it is no longer required.

Related Guides