You can monitor the CPU, GPU, GPU memory, memory, and disk usage of instances for products such as ECS, RDS, MongoDB, and Redis. Tracking and managing instances with low usage over a period of time helps you better manage costs. Some rules in this compliance package use the Cloud Monitor API to retrieve monitoring data. These checks consume your basic Cloud Monitor free quota. For best results, enable Hybrid Cloud Monitoring. For more information about Hybrid Cloud Monitoring billing, see the Cloud Monitor billing documentation. This topic describes the default rules for cost optimization best practices.
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. If an ECS instance is not monitored by Cloud Monitor, this rule is not applicable. The default check period is the last 7 days. This check 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 more information about billing, 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. If an ECS instance is not monitored by Cloud Monitor, this rule is not applicable. The default check period is the last 7 days. This check 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 more information about billing, 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. If an ECS instance is not monitored by Cloud Monitor, this rule is not applicable. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to non-GPU ECS instances, instances whose GPUs are not monitored by Cloud Monitor, or instances with empty monitoring data. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to non-GPU ECS instances, instances that are not monitored by Cloud Monitor, or instances with empty monitoring data. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to instances that are not monitored by Cloud Monitor, instances with empty monitoring data, or instances that are not part of a multi-node deployment cluster. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to instances that are not monitored by Cloud Monitor, instances with empty monitoring data, or instances that are not part of a multi-node deployment cluster. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to instances that are not monitored by Cloud Monitor, instances with empty monitoring data, or instances that are not part of a multi-node deployment cluster. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to RDS instances of the Cluster Edition or Serverless series, instances that are not monitored by Cloud Monitor, or instances with empty monitoring data. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to RDS instances of the Cluster Edition or Serverless series, instances that are not monitored by Cloud Monitor, or instances with empty monitoring data. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to RDS instances of the Cluster Edition or Serverless series, instances that are not monitored by Cloud Monitor, or instances with empty monitoring data. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to instances that are not memory-optimized with a read/write splitting architecture, instances that are not monitored by Cloud Monitor, or instances with empty monitoring data. The default check period is the last 7 days. This check 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 more information about billing, 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. This rule is not applicable to instances that are not memory-optimized with a read/write splitting architecture, instances that are not monitored by Cloud Monitor, or instances with empty monitoring data. The default check period is the last 7 days. This check 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 more information about billing, see the Cloud Monitor billing documentation. |