Checks whether the maximum CPU utilization of each Elastic Compute Service (ECS) instance within a specified time range is greater than or equal to a specified value. If so, the evaluation result is Compliant. This rule does not apply to ECS instances that are not monitored by using CloudMonitor. The default time range is the previous week.
Scenarios
This rule applies when you need to check the CPU utilization of an ECS instance to better understand and optimize system performance. The rule helps you improve resource utilization and system stability.
Risk level
Default risk level: low.
When you apply this rule, you can change the risk level based on your business requirements.
Compliance evaluation logic
Checks whether the maximum CPU utilization of each ECS instance within a specified time range is greater than or equal to a specified value. If so, the evaluation result is Compliant. If the ECS instance is not monitored by CloudMonitor, the evaluation result is Not Applicable. The default detection time range is the previous week. The detection relies on the CloudMonitor APIs and consumes the free quotas for the billable items of CloudMonitor Basic. We recommend that you activate Hybrid Cloud Monitoring to ensure the quality of testing. For more information, see Activate Hybrid Cloud Monitoring. For more information about the billing of Hybrid Cloud Monitoring, see Billing overview.
Rule details
Parameter | Required | Default Value | Description |
relativeTime | Yes | 168 | The period of time during which the maximum CPU utilization of each ECS instance is calculated. Unit: hours. Maximum value: 720 (30 days). Default value: 168 (7 days). |
utilization | Yes | 10 | The maximum CPU utilization of each ECS instance. The value must be greater than or equal to 0 and less than or equal to 100. |
Non-compliance remediation
Monitor the ECS instance by using CloudMonitor. For more information, see Operating system monitoring.