An ECS instance is considered compliant if its maximum memory usage is greater than or equal to a specified value within a defined period. This rule does not apply to ECS instances that are not connected to Cloud Monitor. By default, the detection period is the preceding seven days. The check uses the Cloud Monitor API to retrieve monitoring data, and this process consumes the free quota for basic Cloud Monitor. To ensure the quality of the check, you can enable Hybrid Cloud Monitoring. For more information about billing for Hybrid Cloud Monitoring, see Cloud Monitor billing.
Risk level
Default risk level: Low.
You can change the risk level as needed.
Detection logic
An ECS instance is considered compliant if its maximum memory usage is greater than or equal to a specified value within a defined period. This rule does not apply to ECS instances that are not connected to Cloud Monitor. By default, the detection period is the preceding seven days. The check uses the Cloud Monitor API to retrieve monitoring data, and this process consumes the free quota for basic Cloud Monitor. To ensure the quality of the check, you can enable Hybrid Cloud Monitoring. For more information about billing for Hybrid Cloud Monitoring, see Cloud Monitor billing.
Rule details
Parameter | Description |
Rule name | Check for idle ECS instances based on memory usage |
Rule identifier | |
Tag | ECS |
Automatic remediation | Not supported |
Rule trigger | Scheduled execution |
Trigger frequency | 24 hours |
Supported resource types | ACS::ECS::Instance |
Input parameters | relativeTime (Default: 168) |
Remediation
To remediate non-compliant resources detected by the 'Check for idle ECS instances based on memory usage' rule, see Monitor hosts.