All Products
Search
Document Center

Auto Scaling:Health diagnosis

Last Updated:Feb 04, 2026

The health diagnosis feature of Auto Scaling performs a comprehensive check on your scaling group's configuration. For example, it checks whether the specified vSwitches or security groups are abnormal and whether the instance inventory for the scaling group is healthy. This feature helps you find and fix scaling group issues promptly, which improves the success rate of scale-out and scale-in activities.

Background information

The health diagnosis feature of Auto Scaling checks the status of a scaling group's properties, fees, and quotas. This helps you stay informed about your scaling group's configuration. This topic describes how to trigger the health diagnosis feature.

Trigger method

Description

Manual method

For any created scaling group, regardless of whether it is in the Enabled or Disabled state, you can manually start a health diagnosis request and obtain a health diagnosis report for the scaling group.

Automatic method

For any scaling group in the Enabled state, you can configure the event notification feature of CloudMonitor. The system automatically performs diagnostic checks. CloudMonitor receives event notifications and displays the details of any detected anomalies.

Procedure

Note

Before you use the health diagnosis feature, make sure that you have created a scaling group. For more information, see Create a scaling group.

Diagnosis items and results

The diagnosis items and results are the same regardless of whether you trigger a health diagnosis manually or automatically by configuring CloudMonitor system events. The following table describes the diagnosis items and their results:

Category

Diagnosis item type

Diagnosis item name

Description

Error code

Anomaly details and suggestions

Critical resource anomaly

vSwitch

vSwitch status

Checks whether the vSwitch is available. For example, it checks whether the vSwitch is deleted.

VSwitchIdNotFound

  • Anomaly details: The vSwitch specified in the scaling group does not exist.

  • Suggestions: Confirm whether the vSwitch specified for the scaling group exists. If the vSwitch does not exist, modify the scaling group to use a valid vSwitch.

SecurityGroup

Security group status

Checks whether the security group is available. For example, it checks whether the security group is deleted.

SecurityGroupNotFound

  • Anomaly details: The security group specified in the scaling configuration does not exist.

  • Suggestions: Confirm whether the security group specified in the scaling configuration exists. If the security group does not exist, modify the scaling configuration to use a valid security group.

KeyPair

Key pair status

Checks whether the key pair is available. For example, it checks whether the key pair is deleted.

KeyPairNotFound

  • Anomaly details: The key pair specified in the scaling configuration does not exist.

  • Suggestions: Confirm whether the key pair specified in the scaling configuration exists. If the key pair does not exist, modify the scaling configuration to use a valid key pair.

Quota diagnosis

SlbBackendServerQuota

Number of instances attached to CLB (formerly SLB) instances in the scaling group

Checks whether the number of ECS instances or ECIs attached to the default server group and vServer groups of the CLB (formerly SLB) instances exceeds the quota.

SlbBackendServerQuotaExceeded

  • Anomaly details: The number of backend servers attached to the CLB (formerly SLB) instance exceeds the quota.

  • Suggestions: Remove some backend servers from the CLB (formerly SLB) instance or go to Quota Center to request a quota increase.

AlbBackendServerQuota

Number of instances attached to ALB instances in the scaling group

Checks whether the number of ECS instances or ECIs attached to the server group of the ALB instance exceeds the quota.

AlbBackendServerQuotaExceeded

  • Anomaly details: The number of backend servers attached to the ALB instance exceeds the quota.

  • Suggestions: Remove some backend servers from the ALB instance or go to Quota Center to request a quota increase.

NlbBackendServerQuota

Number of instances attached to NLB instances in the scaling group

Checks whether the number of ECS instances or ECIs attached to the server group of the NLB instance exceeds the quota.

NlbBackendServerQuotaExceeded

  • Anomaly details: The number of backend servers attached to the NLB instance exceeds the quota.

  • Suggestions: Remove some backend servers from the NLB instance or go to Quota Center to request a quota increase.

Billing diagnosis

AccountArrearage

Overdue Account

Checks whether the account has an overdue payment.

AccountArrearage

  • Anomaly details: The account has an overdue payment.

  • Suggestions: Top up your account before you proceed.

Inventory diagnosis

ElasticStrength

Inventory health

Checks the inventory health of the instance types that are specified in the scaling configuration.

ElasticStrengthAlert

  • Anomaly details: The inventory health for the instance types specified in the scaling configuration is poor. This may cause scale-out activities to fail.

  • Suggestions: Optimize the scaling group configuration by changing to a suitable zone or instance type.