The cost optimization best practices compliance package monitors CPU, GPU, GPU memory, memory, and disk usage of ECS, RDS, MongoDB, and Redis instances. By tracking instances with low usage over time, you can identify cost-saving opportunities. Some rules in this package retrieve monitoring data through the Cloud Monitor API and consume your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For more information about billing, see the Cloud Monitor billing documentation.
|
Rule name |
Rule description |
|
An ECS instance is compliant if its maximum CPU utilization over a specified period is greater than or equal to a specified value. Not applicable to instances not monitored by Cloud Monitor. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
An ECS instance is compliant if its maximum disk usage over a specified period is greater than or equal to a specified value. Not applicable to instances not monitored by Cloud Monitor. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
An ECS instance is compliant if its maximum memory usage over a specified period is greater than or equal to a specified value. Not applicable to instances not monitored by Cloud Monitor. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
An ECS instance is compliant if its maximum GPU memory utilization over a specified period is greater than or equal to a specified value. Not applicable to non-GPU ECS instances, instances whose GPUs are not monitored by Cloud Monitor, or instances with empty monitoring data. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
An ECS instance is compliant if its maximum GPU utilization over a specified period is greater than or equal to a specified value. Not applicable to non-GPU ECS instances, instances not monitored by Cloud Monitor, or instances with empty monitoring data. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
An ECS instance is compliant if its runtime in pay-as-you-go mode is less than or equal to a specified value. This rule is not applicable to subscription instances. |
|
|
A MongoDB instance is compliant if its maximum disk utilization over a specified period is greater than or equal to a specified value. Not applicable to instances not monitored by Cloud Monitor, instances with empty monitoring data, or instances not in a multi-node deployment cluster. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
A MongoDB instance is compliant if its maximum memory utilization over a specified period is greater than or equal to a specified value. Not applicable to instances not monitored by Cloud Monitor, instances with empty monitoring data, or instances not in a multi-node deployment cluster. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
A MongoDB instance is compliant if its maximum CPU utilization over a specified period is greater than or equal to a specified value. Not applicable to instances not monitored by Cloud Monitor, instances with empty monitoring data, or instances not in a multi-node deployment cluster. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
An RDS instance is compliant if its maximum CPU usage over a specified period is greater than or equal to a specified value. Not applicable to Cluster Edition or Serverless series instances, instances not monitored by Cloud Monitor, or instances with empty monitoring data. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
An RDS instance is compliant if its maximum disk usage over a specified period is greater than or equal to a specified value. Not applicable to Cluster Edition or Serverless series instances, instances not monitored by Cloud Monitor, or instances with empty monitoring data. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
An RDS instance is compliant if its maximum memory usage over a specified period is greater than or equal to a specified value. Not applicable to Cluster Edition or Serverless series instances, instances not monitored by Cloud Monitor, or instances with empty monitoring data. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
An RDS instance is compliant if its runtime in pay-as-you-go mode is less than or equal to a specified value. This rule is not applicable to subscription instances. |
|
|
A Redis instance is compliant if its maximum memory utilization over a specified period is greater than or equal to a specified value. Not applicable to instances without a memory-optimized read/write splitting architecture, instances not monitored by Cloud Monitor, or instances with empty monitoring data. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |
|
|
A Redis instance is compliant if its maximum CPU utilization over a specified period is greater than or equal to a specified value. Not applicable to instances without a memory-optimized read/write splitting architecture, instances not monitored by Cloud Monitor, or instances with empty monitoring data. Default check period: last 7 days. This rule uses the Cloud Monitor API to retrieve monitoring data and consumes your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For billing details, see the Cloud Monitor billing documentation. |