All Products
Search
Document Center

Create an event-triggered task in auto scaling that indicates insufficient data

Last Updated: Dec 31, 2020

Problem description

The user creates an alarm task in the auto scaling console and notifies that the data is insufficient.

Cause

The auto scaling event-triggered task is monitored based on CloudMonitor data. This problem may be caused by the failure to collect the corresponding ECS server data on the CloudMonitor.

Solution

Alibaba Cloud reminds you that:

  • Before you perform operations that may cause risks, such as modifying instance configurations or data, we recommend that you check the disaster recovery and fault tolerance capabilities of the instances to ensure data security.
  • If you modify the configurations and data of instances including but not limited to ECS and RDS instances, we recommend that you create snapshots or enable RDS log backup.
  • If you have authorized or submitted security information such as the logon account and password in the Alibaba Cloud Management console, we recommend that you modify such information in a timely manner.
  1. Log on to the ECS console. In the left-side navigation pane, click deploy and scale. On the page that appears, click auto scaling.
  2. On the scaling groups page, click the name of the scaling group in group instance configuration.
  3. On the basic information page, click ECS instance list to view and record the ID of the ECS instance.
  4. On the CloudMonitor page in the host monitoring console, enter the ECS instance ID in the search box to check whether the CloudMonitor agent status is running.
  5. If it isn't already installed CloudMonitor plug-in, click tap the install, or log on to the server manually install the manually install method see CloudMonitor ECS monitor plug-in installation method.
  6. If you have installed the CloudMonitor plug-in but do not have monitoring data, use the following steps to troubleshoot the issue.
    • Check whether the monitoring module is installed successfully. This method applies to the CloudMonitor of the new version. The CloudMonitor of the new version is divided into Java version and Go Language version. This article takes Java version as an example.
      • The following process points to the cloudmonitor directory.
      • In the Linux, run the ps-efomgrepcloudmonitor command to check whether there is a cloudmonitor process.
    • Check whether the monitoring module is installed successfully. This method is applicable to the old CloudMonitor.
      • In the Windows system, check whether aegis_quartz.exe processes exist in task manager.
      • In the Linux, run the ps-efomgrepcloudmonitor command to check whether the aegis_quartz process exists.
  7. Verify that the job status in the auto scaling console returns to normal.

Application scope

  • ECS
  • Auto Scaling