New and Updated Features
This topic summarizes both new and updated Densify features introduced in version 12.3.
The Kubernetes Container Optimization page for viewing your container environments has been updated to improve usability. The following changes have been made:
- A new Data tab, shows the aggregated data in a tabular format.
- The Group By feature has been added to the Data tab to provide dynamic data grouping. You can group your data using one of Application, Business Unit, Controller Type, Cost Center, Department, Inventory Code, Namespace, Operational Environment, Owner, Product Code or Project. Your selection is used in the first column of the table and data is displayed accordingly. See
Using the Group By Feature.
- Two additional tabs are provided to drill down and investigate further:
- The Cluster Breakdown tab shows a subset of the information from the top of the page, expanded to show cluster details.
- The Allocation tab shows the current and recommended values CPU and memory resource allocations for the row selected in the primary table at the top of the page.
- You can customize the content of the tabular reports on all 3 (Data, Cluster Breakdown and Allocation) tabs by selecting/deselecting the columns to be displayed.
- You can now sort the content of this table using any of the available columns. See
Sorting Tabular Data.
- A new Search button allows you to search for specific instances, accounts, etc.
- An Export button allows you to export the content to a .CSV file.
- The summary banner at the top of the Summary and Data tabs has been updated:
- A new indicator, the Efficiency Rating provides a high level indication of the health of your container environments.
- Costs and savings are estimated based on configurable cost per CPU and cost per GB of memory. A footnote is displayed at the bottom of the Summary and Data tabs. Contact [email protected] to configure the per unit cost values.
- The Details tab has been removed from the Container main menu. You can now access container details by clicking the "Container Manifests" link from the Summary tab or any of the count hyperlinks on the Data tab. The following changes have been made to the Details page:
- The page has been renamed to Kubernetes Container Optimization Details.
- The container filter has been removed from this page. When you arrive at this page the content is already filtered to show only the records specified by the hyperlink on Summary tab or the count hyperlinks on the Data tab.
- A Back button has been added to take you back to your last page. Using the browser's back button for navigation within Densify exits Densify.
- A new column, "Net Savings ($/month)" has been added to show the monthly savings for the selected container, if the suggested recommendation is made.
- The column "Current Count" has been renamed to "# of Containers".
- The column "No. of Nodes" has been renamed to "# of Nodes"
- A dash (-) is used to indicate when the current CPU or memory request or limit values are not specified. Unspecified values are shown as zero (0) in the "Totals" row.
- The running total block on the Cluster Breakdown and Namespace Breakdown and Details tabs has been updated t o add "Net Savings ($/month)" to show the monthly savings for the clusters, namespaces or selected containers, if the suggested recommendations are made. Savings are estimated based on configurable cost per CPU and cost per GB of memory. Contact [email protected] to configure the per unit cost values.
- Additional information has been relocated to footnotes
- The text previously located on the Summary tab, indicating if there are any containers that are not being analyzed, is now displayed as a footnote, in the lower left corner of the Summary tab.
- Costs and savings are estimated based on configurable cost per CPU and cost per GB of memory. A footnote is displayed at the bottom of the Summary and Data tabs. Contact [email protected] to configure the per unit cost values. This information remains as a popup on the Cluster Breakdown and Namespace Breakdown tabs. Contact [email protected] to configure the per instance cost values.
- The logic for containers, has been updated to make better recommendations when analyzing containers with unspecified request and/or limit values.
Contact Densify Technical Services for details on your policy settings.
The Optimization Overview page for viewing your AWS ASG services has been updated to improve both performance and usability. The following changes have been made:
- You can customize the content of the tabular report by selecting/deselecting the columns to be displayed.
- You can now sort the content of this table using any of the available columns.
- You can use the search button to search the entire page for specific instances, accounts, etc.
- The download .CSV () button allows you to export the content to a .CSV file. The previous export to Excel () button is still available on the ASG In Service Instance Details page.
- The additional data required to associate an ASG with an EKS cluster is now collected and the reference is displayed in the ECS/EKS Reference column.
- The ability to filter systems based on Cost Impact has been removed from the Recommendation filter. This option was removed from the AWS > EC2, Azure and GCP Optimization Overview dashboards in a previous release (12.1.10). See
Using the Recommendation Filter Menufor details.
- Total savings based on making all of the recommended changes is now provided at the bottom of the tabular view.
The minimum set of permissions in the IAM policy, required to perform CloudWatch data collection has been updated to add:
The “cloudformation:DescribeStackResource” permission is used by the current method of data collection. The “cloudformation:DescribeStackResources” is required for the new data collection framework. This allows Densify to make fewer API calls and improve the overall efficiency of data collection.
Data collected from GCP has been streamlined to improve performance and limit the collection of metrics that are not used by the Densify analysis.
ASG entities can now be linked as children of a Kubernetes Node Group or Cluster entity resulting in improved answer quality. The ASGs are analyzed together with their linked EKS node groups and a multi-step linking process does the following:
- Matches the Kubernetes Cluster Names from the Data Forwarder to Cluster Names from AWS CloudWatch audit;
- Counts the number of ASGs and Node Groups per cluster;
- Links the ASGs to Node Groups or Clusters.
These changes align EKS-aware recommendations for ASGs with similar recommendations for ECS-aware ASGs.
The following updates to the public cloud metadata have been made to remain current with the latest vendor pricing and instance availability across regions:
- AWS Metadata Updates:
- The pricing has been updated and is correct as of July 16, 2021;
- Added support for RHEL-HA systems.
- Azure Metadata Updates:
- The pricing has been updated and is correct as of July 22, 2021;
- Added the new Sweden-central and Sweden-south regions;
- Added Reserved 5-year pricing types for the instances that support it;
- Added the following new instances:
- GCP Metadata Updates:
- The pricing has been updated and is correct as of July 16, 2021;
- Added the new Australia-southeast2 region.
You may observe minimal changes to instance pricing.
A number of updates have been made to reduce the time required to load and process billing data. Additional indexes have been added to specific database tables to improve the performance of configuring and displaying various reports in the Cloud Cost Intelligence module.
As part of these updates the Reserved Instances tab on the Public Cloud Optimization for AWS dashboard has been deprecated. Extensive reporting features for AWS Reserved Instances are provided in the Cloud Cost Intelligence module. See
The benchmark lookup tables have been updated with new values to improve recommendation results:
- Existing values have been updated and new systems have also been added.
- Added support for IBM Power 9 S914
You can now evaluate and customize the set of attributes that are used for the Group By feature. Densify can assist in determining 'Group By' candidates. Once the metadata of interest has been established then with customer input, Densify can enable these as drop-down options in the Densify UI and used to view your data on the following pages:
- Public Cloud Optimization Overview > Data tab
- Containers > Data tab
The Densify Connector has been updated with the following feature:
- Updated version of Java—AdoptOpenJDK JRE 11.0.10 (jdk11.0.10_9) is installed automatically with the Densify Connector..