Announcing new idle VM recommendation configuration option in Google Cloud
Active Assist’s Idle VM recommendations can help you save money and resources by identifying and deleting idle VMs. Today, Google are excited to announce a new configuration option for idle Virtual Machine recommendations, giving you more control over how idle VMs are identified and recommended for deletion.
Google Cloud generates idle VM recommendations automatically based on system metrics gathered by the Cloud Monitoring service. Previously, the observation period for idle VM recommendations was fixed at 14 days. As such, no matter what kind of resources you monitored (development, test or production), you always got recommendations based on a two-week timeframe. That was a good approach for most workloads, but we heard from customers that they would like to adjust their configurations for different projects.
With the new configuration option, you can now specify a different observation period, ranging from 1 day to 14 days. This gives you more flexibility to tune idle VM recommendations to meet your specific needs. For example, you can now
- Use a shorter observation period if you want to be less conservative and potentially save more costs
- Use a longer observation period if you want to receive recommendations that are not affected by short-term fluctuations in your workload.
HTTP method and URL example:
The command returns the recommender configuration, including the subfield that you can
You can also use the gcloud recommender recommender-config update command.
For example, to set the observation period to 7 days (604800s), provide a configuration file with this value using the following command:
gcloud recommender recommender-config update \ google.compute.instance.IdleResourceRecommender \
--project=your_project_number --location=your_zone \