An ECS disk is considered compliant if its maximum disk usage within a specified period is greater than or equal to a specified value. If an ECS instance is not connected to Cloud Monitor, the check is not applicable to the instance. The default check period is the last 7 days. The check uses the Cloud Monitor API to retrieve monitoring data and consumes the free quota for basic monitoring. To ensure the quality of the check, enable Hybrid Cloud Monitoring. For more information about billing for Hybrid Cloud Monitoring, see Billing of Cloud Monitor.
Risk level
Default risk level: Low.
You can change the risk level as needed.
Detection logic
An ECS disk is considered compliant if its maximum disk usage within a specified period is greater than or equal to a specified value. If an ECS instance is not connected to Cloud Monitor, the check is not applicable to the instance. The default check period is the last 7 days. The check uses the Cloud Monitor API to retrieve monitoring data and consumes the free quota for basic monitoring. To ensure the quality of the check, enable Hybrid Cloud Monitoring. For more information about billing for Hybrid Cloud Monitoring, see Billing of Cloud Monitor.
Rule details
Parameter | Description |
Rule name | Idle disk check for ECS instances |
Rule identifier | |
Tag | ECS |
Automatic remediation | Not supported |
Rule trigger | Periodic |
Trigger frequency | 24 hours |
Supported resource types | ACS::ECS::Instance |
Input parameters | relativeTime (Default value: 168) |
Remediation guide
To remediate non-compliant resources detected by the "Idle disk check for ECS instances" rule, see Monitor hosts.