Discount coverage chart

Note:

This topic describes features that are available in the new design of the user interface. This new design is enabled by default. If you switched to the legacy design, click New Feature Toggle button in the navigation bar of the user interface and then turn on the toggle to re-enable the new design. For more information, see New Design for the User Interface.

This chart shows the percentage of cloud workloads (VMs and RDS database servers) covered by discounts. For VMs covered by discounts, you can reduce your costs by increasing coverage. To increase coverage, you scale VMs to instance types that have existing capacity.

Discount Coverage chart

To identify VMs that are good candidates for discounted pricing, Turbonomic analysis considers the history of a VM (by default, the last 21 days), and it looks for:

  • Activity

    If the VM's VCPU utilization percentile is 20% or higher, then Turbonomic considers it an active VM.

  • Stability

    If there have been no start, stop, or resize actions for the VM for 16 of the last 21 days, then Turbonomic considers it stable.

If the current discount inventory cannot support the VM, or if supporting it would exceed your desired coverage, then Turbonomic can recommend purchasing additional discounts.

Timeframe

The chart shows daily data points and supports the following timeframes:

  • Last 7 Days

  • Last 30 Days

AWS EC2/RDS reserved instances and compute savings plans

Turbonomic uses data exports from AWS to calculate Reserved Instance (RI) and Compute Savings Plan coverage for both standard and GovCloud workloads. Turbonomic supports a data export created at the management account, but not member accounts. For Turbonomic to use these data exports, you must add a billing target in the Target Configuration page.

The chart shows historical data. Data for the current day may not be available until the cloud provider has exported it fully.

Hover on a data point in the chart to see the following information:

  • The date and time for the data point

  • The percentage of coverage. For RIs, coverage is based on normalization factors.

    Normalization factor is a measure of RI capacity that you can use to compare or combine the capacity for different instance families.

    Turbonomic measures RI coverage in terms of normalization factors. It compares the number of RIs calculated as normalization factors that cover workload capacity with the total number of normalization factors for a given Turbonomic scope. Each workload is assigned normalized units depending on its instance type.

Points to consider:

  • Scope

    • If you set the scope to a specific AWS account, the chart shows the RI coverage for the workloads for the account and any RIs for the billing family.

    • For AWS GovCloud, you can set the scope to the global environment or the standard account/billing family associated with GovCloud.

  • RIs

    In AWS, you can turn off RI discount sharing for specific accounts. These accounts will not share any discounts with other accounts. Turbonomic does not recognize RI coverage or utilization for these accounts. For example, the RI Coverage and RI Utilization charts will show zero values.

Azure reservations and savings plans

Turbonomic uses billed cost data from Azure to calculate reservation and savings plan coverage for workloads. For Turbonomic to use billed cost data, you must add an Azure Billing target in the Target Configuration page.

Note:

The use of billed cost data to calculate reservation or savings plan coverage for Azure Government workloads is not supported.

The chart shows historical data. Data for the current day may not be available until the cloud provider has exported it fully.

Hover on a data point in the chart to see the following information:

  • The date and time for the data point

  • The percentage of coverage

    • For reservations, the percentage of coverage is based on ratios.

      Ratio refers to the number of Azure reservation units that cover workload capacity compared to the total number of reservation units for a given Turbonomic scope. Each workload is assigned reservation units based on its instance type.

    • For savings plans, the percentage of coverage is based on billed cost data.

If you set the scope to a specific Azure subscription, this chart shows the following:

  • Reservation or savings plan coverage for the workloads for the subscription

  • Shared reservations or savings plans

  • Single-scope reservations or savings plans owned by the subscription

Google Cloud committed use discounts

Turbonomic uses billing data from Google Cloud to calculate CUD coverage for VM vCPU (cores) and VM memory. For Turbonomic to use billing data, you must add a Google Cloud Billing target in the Target Configuration page.

The chart shows historical data. Data for the current day may not be available until the cloud provider has exported it fully.

Hover on a data point in the chart to see the following information:

  • The date and time for the data point

  • The percentage of coverage

Points to consider:

  • CUD coverage in this chart and in the Google Cloud console may not match for the following reasons:

    • Turbonomic uses UTC, while the Google Cloud console uses local time.

    • CUD coverage for VMs running custom machine types is reported by Google Cloud but not by Turbonomic. If the chart's scope includes these VMs, aggregated data may not match the data shown in Google Cloud. If the chart is scoped solely to these VMs, the chart will not display data.

    • Google Cloud reports CUD coverage for resource reservations, which Turbonomic does not monitor. When CUDs cover both VMs and resource reservations, Google Cloud reports coverage for both, while Turbonomic only reports coverage for VMs.

  • When you configure a billing export in Google Cloud, you can choose to export standard or detailed usage cost data. Detailed usage cost data is recommended because it includes granular data that Turbonomic can display in charts, such as discount coverage for individual VMs.

    If you exported standard usage cost data and configured your Google Cloud Billing target to use this data:

    • Coverage data in the chart is only available for scopes that are larger than individual VMs, such as projects or folders. This is because standard usage cost data does not include CUD coverage for individual VMs.

    • Turbonomic uses retail pricing to calculate coverage. This may result in an underestimation of the coverage if the negotiated price for a machine type is lower than the retail price.

    Note:

    The Google Cloud Billing target uses standard usage cost data if you disabled the Enable Resource Level Detail From Cost Export Table option in the Target Configuration page for the target.

  • When coverage reaches 100%, a rounding issue might result in a value that is slightly higher than 100% (such as 100.01%).