Viewing Cloud Optimization Reports

Viewing Cloud Optimization Reports

#380540

The various optimization opportunity reports summarize recommendations specifically for a public cloud service type. Services that do not have adequate data to perform the required analyses are not included in these reports. Components of the cloud service optimization opportunity reports are described below.

Note: Components for Reserved Instances and Auto Scaling groups optimization opportunity reports are described in their own topics. See Viewing Reserved Instances and Working with Auto Scaling Groups for details.

Table: Public Cloud Optimization Report Components

Component / Column Name

Description

Included in Reports

Count

The number of instances listed in the Count column is a hyperlink that takes you to the Instance Optimization Details page for the selected instance group. For more information on this page, see Understanding the Instance Optimization Details Report.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Overall Status

Identifies the overall status of the optimization results based on the Optimization Type and potential $ Savings/Month:

Optimal

These instance types are currently optimal. The Optimization type is just right and there are no costs savings for this group.

Identified Risk

These instance types are at risk. This status occurs when the savings amount is less than $0 (i.e. you need to spend money to mitigate risk).

Identified Risk status is also indicated when the savings amount is $0, but optimization type is upscale, upsize, or upsize to optimal family. This situation occurs when services are inactive, however, they will need to be upscaled or upsized to mitigate risk when they resume activity.

Savings Opportunity

These instance types can provide saving opportunities that greater than $0.

Savings opportunity status is also indicated when the savings amount is $0, but optimization type is terminate, modernize, modernize to optimal family, downscale, downsize, or downsize to optimal family. This situation occurs when services are inactive, but have a recommendation of terminate, modernize, downsize or downscale when they resume activity to save money.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Optimization Type

The recommended action for the group of instances. See Optimization Type Color-Coding Summary for a description of each recommendation.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Current Instance Type

Based on the data collected, the current catalog instances is listed.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Recommended Instance Type

Based on optimization analysis, the recommended catalog instances is listed.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Defer Recommendation Until Current RI Coverage Expires

Defer recommending an instance type change until reserved instance coverage for this instance group expires. Values include:

  • Yes—defer instance type recommendations due to RI coverage;
  • No—do not defer instance type recommendations; this is also the case for "Terminate" recommendations;
  • "-" —not applicable; no instance type change is listed for "Just Right" recommendations.

This field is based on AWS Defer Recommendation settings. Contact your Cloud Advisor or support@densify.com to review your AWS Defer Recommendation settings.

  • AWS > EC2, RDS

Current RI Expiry Date

If Defer Recommendation Until Current RI Coverage Expires = "Yes", then the expiry date(s) of the reserved instances(s), which are currently providing coverage for this group of instances, are displayed.

Note: RI expiry dates are not displayed for instance groups with Optimization Type = " Just Right" or "Terminate".

  • AWS > EC2, RDS

Current Estimated Cost ($)

The current estimated cost is determined by adding all the current estimated cost of each instance in the group. See Current Estimated Cost ($) in the Instance Optimization Details Report.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Recommended Estimated Cost ($)

The recommended estimated cost is calculated by adding all the recommended estimated cost of each instance in the group. See Recommended Estimated Cost ($) in the Instance Optimization Details Report.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

$ Savings/Month

The estimated current and recommended instance cost is used to calculate savings per month (i.e. current estimated cost - recommended estimated cost).

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Effort

[High|Medium|Low|None]

This column describes the effort required to investigate and implement the Densify recommendations. The displayed group effort is an average of all the calculated efforts for each instance (or service) in the group. Effort for each instance is calculated by rule-driven analytics based on factors (such as family change, storage change, data quality checks, feature changes, etc.) that can be configured in the policy settings and rule set which captures best practices.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Current vCPUs

The current value for CPU allocation.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Recommended vCPUs

The recommended value for CPU allocation.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Current Memory Allocation (GB)

The current value for memory allocation.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Recommended Memory Allocation (GB)

The recommended value for memory allocation.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Footnote

A footnote at the bottom of the optimization opportunity report displays the total number of instances (subject to any guest filters applied) of the specific public cloud service type. The number of instances is a link to the Instance Optimization Details page, showing an aggregate report that contains all recommendations of that service type in one view. For details on this page, see Understanding the Instance Optimization Details Report.

Note: If recommendation filters are applied, the total number of instances on the last page of the optimization report might not be the same as the total number of instances in the footnote; this is because the recommendation filters are not reflected in the footnote total.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Sort By

You can change the instance group order of the tabular optimization opportunity report by selecting one of the sort options in the top Sort By dropdown list. For details on sorting behavior, see Sorting Options.

Note: If there is no data in the optimization opportunity tabular report, the Sort By section is not displayed.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Summary Total

In the top-right corner of tabular optimization opportunity reports, the total number of Instances and the Savings/Month for implementing the recommendations are displayed. The total number of instances displayed is a total of all the analyzed instances with guest and recommendation filters applied. The amount of savings per month is based on filtered data and can be negative if there is higher upsizing cost.

Note: If there is no data in the optimization opportunity tabular report, the Summary Total section is not displayed.

  • AWS > EC2, RDS, Spot Instances
  • Azure > Virtual Machines
  • GCP > Compute Engine

Optimization Type Color-Coding Summary

Table: Optimization Type Color-Coding Summary

Optimization Type

Description

Just Right

This instance is optimally sized for the workload.

Upsize Recommendations

In general upsize recommendations incur additional costs. The cost increase is determined by comparing on-demand pricing. The increased cost is required to alleviate application risk. It is possible that if you have an RI for the recommended upsize instance, there could be cost savings. This would still be an upsize recommendation.

Upsize - Optimal Family

This instance should be upsized to a more optimal instance family. This will improve the workload's performance and reduce risk.

If the workload can be moved to larger instance in a different family and still reduce cost, this then becomes a Modernize recommendation.

Upsize

This instance should be upsized to an instance within the same instance family. The hosted workload needs an instance with more CPU and\or memory resources.

e.g. r3.large to r4.xlarge, both are in the "Memory Optimized r" instance family.

Upscale

This recommendation applies to ASGs only and indicates the ASG needs increase compute capacity by adjusting the maximum group size.

It may be more cost effective to use a larger instance for this ASG.

Terminate & Downsize Recommendations

Downsize recommendations reduce the allocated resources as your workload has likely been over-provisioned. Once the recommendation has been determined from CPU and memory utilization it is then further verified against policy-defined limits. before the downsize or terminate recommendations are made.

Terminate

This instance should be terminated, as it is idle. An instance is determined to be idle if it has very low CPU utilization, network and disk I/O over an extended period of time. This will save you money.

Downsize - Optimal Family

This instance should be downsized to an instance belonging to an instance family that more closely suits your workload's utilization.

When you downsize, CPU and\or memory will be decreased to better suit your workloads. Utilization will improve with no impact on performance. This will save you money.

Downsize

This instance should be downsized to an instance within the same instance family.

As indicated above, CPU and\or memory will be decreased to better suit your workloads. Utilization will improve with no impact on performance. This will save you money.

Downscale

This Auto Scaling group should be downscaled to decrease the compute capacity by adjusting the minimum group size.

Modernize Recommendations

Modernize recommendations move your workload to a more modern instance type without changing the resource allocation, cost or performance, at a minimum. Your costs could decrease and/or you may benefit from potential utilization and performance improvements.

Modernize - Optimal Family

This instance should be modernized to an instance belonging to a more optimal instance family. The cost of the new instance type will be less than the existing cost.

Allocated resources are not being removed and moving to an instance with more current hardware, you may also benefit potential utilization and performance improvements.

When you modernize, you will not decrease performance but will decrease cost.

Modernize

This instance should be modernized to an instance within the same instance family. The cost of the new instance type will be less than the existing cost and as indicated above you may also get utilization and performance improvements.

For example, moving to a new generation of the same instance family (e.g. m3.large to m4.large).

Filtering Options

You can filter the optimization opportunity reports by guests and instance attributes, as well as by recommendations.

Note: The global filter is not applicable to the cloud optimization opportunities dashboards and is not accessible on these pages.

Filtering by Guest Attributes

You can filter guests using a set of attributes (e.g. Business Unit, Application).

This type of filtering is supported on the optimization opportunities dashboard tabs, as well as the Instance Optimization Details page when navigating from the Count column. The guest filters selected are persistent across platforms for those pages that support the guest filters (i.e. guest filters selected for AWS EC2 will apply to the AWS RDS, AWS Spot Instances, as well as the AWS Instance Optimization Details reports).

For details, see Using the Guest Filter.

Filtering by Recommendation

You can filter instances based on recommendations using the Recommendation Filter Menu. This filter allows you to narrow the results of your optimization reports based on recommended optimization type, effort required, monetary impact, and service characteristics. The resulting filtered report can be exported for external analysis using the Export to Excel () tool.

For details, see Using the Recommendation Filter Menu.

Sorting Options

Optimization opportunity reports in tabular format can be sorted by the following fields:

  • Overall Status & Optimization Type (default option)
  • $ Savings/Month High to Low
  • $ Savings/Month Low to High
  • Effort None to High
  • Effort High to None
  • Current RI Expiry Date

Guest systems are sorted based on the selected sort option with any guest or recommendation filter already applied to the displayed results. The sorted report can be exported (in the same sort order) for external analysis using the Export to Excel tool.

The selected sort option is saved within the same session and will also be applied when you navigate to another tabular optimization opportunity report within the same public cloud environment supporting the sort option. For example, if you specify that the sort option is Effort High to None in the AWS EC2 optimization opportunity report, then when you navigate to the AWS RDS optimization opportunity report, the sort option still remains Effort High to None. However, if you navigate to the Azure Virtual Machines optimization opportunity report, the sort option will change to the default or saved Azure sort option. When you logout of Densify, the sort option is reset to default sorting.

Table: Sorting Option Descriptions

Sort Options

Description

Overall Status & Optimization Type

(default)

By default, the tabular optimization opportunity reports are ordered based on this option. Instances are first sorted by Overall Status, in the following order:

  1. Savings Opportunity
  2. Optimal
  3. Identified Risk

If overall status are the same, then the secondary sort key is by Optimization Type, in the following order:

  1. Terminate
  2. Modernize
  3. Modernize - Optimal Family
  4. Downsize
  5. Downsize - Optimal Family
  6. Just Right
  7. Upsize
  8. Upsize - Optimal Family

If overall status and optimization types are the same for the instances, then the tertiary sort key is by instance Count, in descending order.

$ Savings/Month High to Low

Sort by the $ Savings/Month field, from largest savings to lowest savings. If the savings are the same, then secondary sort is performed on Effort, from None to High.

$ Savings/Month Low to High

Sort by the $ Savings/Month field, from lowest savings to largest savings. If the savings are the same, then secondary sort is performed on Effort, from None to High.

Effort None to High

Sort by Effort, from None to High. If the effort is the same, then secondary sort is performed on $ Savings/Month, from largest savings to lowest savings.

Effort High to None

Sort by Effort, from High to None. If the effort is the same, then secondary sort is performed on $ Savings/Month, from largest savings to lowest savings.

Current RI Expiry Date

Sort from earliest to latest date. Instance groups with no RI expiry dates are displayed at the end of the list.