In this release Densify now analyzes your Azure Virtual Machine Scale Sets (VM Scale Set) and generates recommendations for the optimal instance type and minimum and maximum size settings. The following changes have been made:

• The Azure \results endpoint has been updated to return details of analyzed VM Scale Set.
• For VM Scale Sets with maximum size=1 returned fields are the same as other VMs, but with "serviceType" set to "VM Scale set" i.e.
• All other returned elements are similar to those for a virtual machine service (i.e. min/max group size values are not returned).
• In the Densify UI, these VM Scale Sets appear on the VM tab.
• The Impact Analysis and Recommendation Report report is not currently available for VM Scale Sets with maximum size >1. Additionally the catalog map features are not available for VM Scale Sets with maximum size > 1.
• The following API calls are not currently supported for VM Scale Set.
• Get analysis system list;
• Get systems using a filter;
• Get details for oneVM Scale Set.

See Analysis: Azure Recommendations

The Azure \results endpoint has been updated to return the "region" field for all supported instance types, including VM Scale Set.  See Analysis: Azure Recommendations.

The /webhook/analysis resource has been updated to support AWS ASGs and Azure VMs including VM Scale Set. See Analysis: Webhook.

• Both the AWS and Azure \results endpoints have been updated to return the "scalingPolicies" field when analyzing ASGs or VM Scale Set with max size >1.
• For Terminate recommendations the \results endpoint for all cloud providers has been updated to show scalingPolicies = “Terminate”, instead of displaying “-“. The character, “-“ is still used in the Densify Console pages to indicate the scalingPolicies value when Optimization Type=Terminate'.
• When determining the scaling policy for both ASGs and VM Scale Setthe logic has been updated to consider changes to the minimum and maximum group size changes.

See the following topics for details:

• Analysis: AWS Recommendations;
• Analysis: Azure Recommendations.

In this release Densify introduces a feature that improves analysis performance. As a result, the following changes have been made to the API:

• Overriding the default policy instance when creating the analysis is no longer supported, through the API.
• Specifying the policy instance, when running an ad hoc analysis is no longer supported, through the API.

Contact [email protected] for details on changing or tuning the default policy.

The following changes have been made to the Densify API to expand the functionality of the catalog map:

• New Governance API Endpoint—The endpoint, /systems/<id>/analysis-details provides a list of suitable instance types for a specified workload, in addition to the recommended optimal instance type.
• Spend and Effort Tolerance—Specify cost and effort limits to customize the list of possible targets to better suit your requirements.
• Additional Parameters for the Governance API—Eight new properties are returned that provide details of each instance type.
• Strict Instance Type Naming Conventions—To support platform-specific automation tools, where strict naming conventions are required, when supplying an instance type, each cloud manufacturers’ exact instance type naming convention is now maintained. Exact instance type names can be obtained using the /systems/<id>/analysis-details endpoint.

See Systems: Analysis Details.

The 30/60-day historical audits have been disabled by default. This only impacts new customers with more than 60-days of AWS data or 30-days of Azure/GCP data.

The ability to disable the historical AWS audits was provided in a previous release, to address performance issues that may be encountered during initial collection of historical data in very large environments.