The health diagnosis feature of Auto Scaling helps you comprehensively check and understand the health status of your scaling group in real time. This way, you can detect and resolve issues at the earliest opportunity. This improves the success rate of scale-outs or scale-ins.

Prerequisites

A scaling group is created. For more information, see Create scaling groups.

Background information

You can use the health diagnosis feature of Auto Scaling to diagnose your scaling group attributes, billing, and quota. You can also use the feature to keep updated on the latest configurations of your scaling group. To use the health diagnosis feature, you can use one of the following methods:
  • Manual health diagnosis: You can initiate a health diagnosis request to obtain the health report of the scaling group regardless of whether your scaling group is in the Enabled or Disabled state. For more information, see Manually initiate a health diagnosis request.
  • Automatic health diagnosis: If your scaling group is in the Enabled state, you can use the event notification feature of CloudMonitor together with automatic health diagnosis. When Auto Scaling checks the health status of your scaling group, CloudMonitor receives event notifications and displays the details of exceptions. For information about how to replace images, see Configure an automatic health diagnosis task.

Manually initiate a health diagnosis request

  1. Log on to the Auto Scaling console.
  2. Find a scaling group and use one of the following methods to go to the scaling group details page:
    • Click the ID of the scaling group in the Scaling Group Name/ID column.
    • Click Details in the Actions column.
  3. In the upper part of the scaling group details page, click the Health Check tab.
  4. Click Diagnose Now.
    When the status in the Diagnostic Progress column changes from Diagnosing to Completed, the health diagnosis is complete. Then, you can view information such as the report ID and diagnostic status.
  5. In the Actions column of the report, click View Report.
    • If a similar report is displayed as shown in the following figure, no exceptions are detected and your scaling group is healthy. Figure - Normal
    • If a similar report is displayed as shown in the following figure, exceptions are detected. Resolve the issues based on the exception details and troubleshooting suggestions. The following figure shows that the vSwitch is abnormal. Figure - Abnormal
    Note If you want to delete a report after you view the content of the report, click Delete Report in the Actions column. In the Delete Report message, click OK.

Configure an automatic health diagnosis task

Before you configure an automatic health diagnosis task, make sure that your scaling group is in the Enabled state. For more information, see Enable or disable scaling groups.

  1. Log on to the Auto Scaling console.
  2. Find a scaling group and use one of the following methods to go to the scaling group details page:
    • Click the ID of the scaling group in the Scaling Group Name/ID column.
    • Click Details in the Actions column.
  3. In the upper part of the scaling group details page, click the Notification Rules tab.
  4. Click Create Advanced Rule.
  5. In the Create Notification Rule dialog box, configure a notification method and specify a notification event, and then click OK. The following table describes the parameters.
    ParameterDescription
    Notification MethodSet the value to CloudMonitor.
    EventSelect Scaling Group Diagnosis.
  6. Find the notification rule that is created in Step 5 and click CloudMonitor in the Notification Method column to go to the System Event page.
  7. On the Event Monitoring tab, select Auto Scaling and click Search to query exceptions that are detected during the health diagnosis.
    Note CloudMonitor updates the health diagnosis result every 2 hours.
    • If no exceptions are detected in your scaling group during the health diagnosis, no data is displayed on the CloudMonitor page.
    • If exceptions are detected in your scaling group during the health diagnosis, your CloudMonitor page is displayed as shown in the following figure. In the figure, the exception is that the vSwitch is deleted. Figure - CloudMonitor
      In the Actions column of the Auto Scaling system event, click Details to view the details of the event. Sample event details:
      {
          "details": [
              {
                  "diagnoseType": "VSwitch",
                  "errorCode": "VSwitchIdNotFound",
                  "resourceId": "vsw-bp1ech44ks0w4zq4u****",
                  "status": "Critical"
              }
          ]
      }

Health diagnosis items and results

The health diagnosis items and results are identical regardless of whether you manually initiate a health diagnosis request or configure an automatic health diagnosis task. The following table describes the health diagnosis items and results.
CategoryItem typeItem nameDescriptionError codeException and troubleshooting suggestion
Critical resource exceptionvSwitchvSwitch statusChecks whether a specific vSwitch can function as expected. For example, if a vSwitch is deleted, the vSwitch cannot provide services and an exception occurs. VSwitchIdNotFound
  • Exception details: The specified vSwitch of the scaling group does not exist.
  • Suggestion: Check whether the vSwitch exists. If the vSwitch does not exist, associate a valid vSwitch with the scaling group.
SecurityGroupSecurity group statusChecks whether a specific security group can function as expected. For example, if a security group is deleted, the security group cannot provide services and an exception occurs. SecurityGroupNotFound
  • Exception details: The specified security group of the scaling group does not exist.
  • Suggestion: Check whether the security group exists. If the security group does not exist, associate a valid security group with the scaling group.
KeyPairKeyPair statusChecks whether a specific key pair is available. For example, if a key pair is deleted, you can no longer use the key pair. KeyPairNotFound
  • Exception details: The specified key pair of the scaling group does not exist.
  • Suggestion: Check whether the key pair exists. If the key pair does not exist, specify a valid key pair for the scaling group.
Quota checkSlbBackendServerQuotaNumber of servers attached to the associated CLB instancesChecks whether the number of ECS instances or elastic container instances that are attached to the associated Classic Load Balancer (CLB, formerly known as SLB) instances as backend servers exceeds the quota. SlbBackendServerQuotaExceeded
  • Exception details: The number of backend servers that are attached to the associated CLB instances exceeds the quota.
  • Suggestion: Detach excess backend servers from the associated CLB instances, or go to Quota Center to request a quota increase.
AlbBackendServerQuotaNumber of servers attached to the associated ALB instancesChecks whether the number of ECS instances or elastic container instances that are attached to the associated Application Load Balancer (ALB) instances as backend servers exceeds the quota. AlbBackendServerQuotaExceeded
  • Exception details: The number of backend servers that are attached to the associated ALB instances exceeds the quota.
  • Suggestion: Detach excess backend servers from the associated ALB instances, or go to Quota Center to request a quota increase.
NlbBackendServerQuotaNumber of servers attached to the associated NLB instancesChecks whether the number of ECS instances or elastic container instances that are attached to the associated Network Load Balancer (NLB) instances as backend servers exceeds the quota. NlbBackendServerQuotaExceeded
  • Exception details: The number of backend servers that are attached to the associated NLB instances exceeds the quota.
  • Suggestion: Detach excess backend servers from the associated NLB instances, or go to Quota Center to request a quota increase.
Billing diagnosisAccountArrearageOverdue paymentsCheck whether your Alibaba Cloud account has overdue payments. AccountArrearage
  • Exception details: The Alibaba Cloud account has overdue payments.
  • Suggestion: Add funds to the Alibaba Cloud account before you proceed.
Inventory diagnosisElasticStrengthInventory sufficiencyCheck whether the instance types that are specified in the scaling configuration are sufficient. ElasticStrengthAlert
  • Exception details: The instance types that are specified in the scaling configuration are in sufficient. This may cause scale-out failures.
  • Suggestion: Optimize the settings in the scaling configuration. For example, you can specify other zones that have sufficient instance types.