Google Cloud actions

Turbonomic monitors the state and performance of your workloads and then recommends actions to optimize these workloads at the lowest possible cost.

Note:

Use the Potential Savings and Necessary Investments charts to view pending actions and evaluate their impact on your cloud expenditure.

Historically-informed action generation for Google Cloud virtual machines

Turbonomic can recommend VM scale actions informed by historical utilization data on the same day a new Google Cloud target is added.

To take advantage of this feature, add at least one Google Cloud target. The service account for this target requires the logging.logEntries.list permission and all the permissions listed in this topic.

Note:

Currently, VM scale actions consider historical utilization of all resources, except I/O throughput.

Actions for virtual machines

Turbonomic supports the following actions:

  • Scale

    Change the VM instance to use a different instance type or tier to optimize performance and costs.

  • Discount-related actions

    If you have a high percentage of on-demand VMs, you can reduce your monthly costs by increasing Committed Use Discount (CUD) coverage. To increase coverage, you scale VMs to instance types that have existing capacity.

    Actions to purchase CUDs will be introduced in a future release.

  • Stop and start (also known as 'parking' actions)

    Stop a VM for a given period of time to reduce your cloud expenses, and then start it at a later time.

  • Reconfigure

    Google Cloud provides a specific set of machine types for each zone in a region. If you create a policy that restricts a VM to certain machine types and the zone it is currently on does not support all of those machine types, Turbonomic will recommend a reconfigure action as a way to notify you of the non-compliant VM.

For details, see Actions for Google Cloud VMs.

Actions for volumes

Turbonomic supports the following actions:

  • Scale

    Scale attached volumes to optimize performance and costs.

    For scale actions that require a tier change or actions that scale up IOPS for extreme persistent disks, Google Cloud requires a snapshot of the volume and the creation of a new volume based on the snapshot. When a new volume is created from a snapshot, it effectively has a new identity, thus resulting in the loss of historical utilization and cost information for that volume.

  • Delete

    Delete unattached volumes as a cost-saving measure. Turbonomic generates an action immediately after discovering an unattached volume.

For additional information, see Cloud Volume Actions.