Basic authentication for accessing the Densify API has been deprecated in this release. Only token-based authentication is supported, for enhanced security. See Authorize for details.

To ease the transition of any integrations, basic authentication functionality can temporarily be extended to September 30th, 2023. Contact [email protected] for details.

The Supply and Demand Postman collection has been updated in this release. The updated supply and demand API examples is provided as a separate collection. See Postman Collection.

The /analysis endpoint for AWS has been updated to support execution of the 60-day historical audit, on an ad hoc basis.

The ability to disable the 60-day historical audit was provided in a previous release to address performance issues that may be encountered during initial data collection in very large AWS environments. The option to run the 60-day historical audit has always been available through the Analysis Console. This update extends the existing /analysis endpoint to trigger a one-time, 60-day historical audit for an AWS account that has existing daily audits configured.

See Analysis: AWS Analyze for details.

The following updates have been made in this release:

• During routing of incoming workloads, any clusters that are undergoing sensor data recalculation (i.e. sensor capacity data is not available) are now excluded from consideration as a hosting option. This ensures that valid sensor capacity data is used when making routing decisions. See Routing Requests.
• You now have the option to select a sensor placement strategy for routed workloads. In addition to the existing balancing strategy that distributes incoming workloads across all suitable datastores, you now have the option to fill a datastore and then move to the next one. You can specify a sensor placement strategy when submitting a routing request (via the API) or you can define the strategy globally using a configuration setting. See Routing Requests.

The URLs for the Densify, Analysis Console, as well as the JasperReports Server artifacts have been updated to remove references to CIRBA. Use the following URLs to access the various consoles:

• Densify 2022: <customer_name>.densify.com/densify
• Analysis Console: <customer_name>.densify.com[:8443]/admin
• JasperReports Server artifacts have been updated to rename "CIRBA" to "densify" in the folder hierarchy.

The /systems endpoint has been updated to include the ecs_svc object. The following operations are supported for systems with object type=ecs_svc:

• /systems GET
• /systems/<ID> GET
• /systems/<ID>/attributes PUT
• /systems/<ID>/attributes DELETE

See Systems for details of using the /systems endpoint.

When accessing the Densify user interface a malicious actor cannot perform a brute force attack because the user account is locked after three failed login attempts for a predefined timeout period.

Since users can also authenticate through the ‘authorize’ API call using the same credentials, the safeguards in place that reduce the risk of a successful brute-force attack have been updated. The delay between failed attempts now doubles and if an attempt is made during the lockout period, the delay is doubled, again. See Authorize

When using either API System or Results resources, you no longer need to wait for the reporting database refresh to complete before requesting the Impact Analysis and Recommendation Report. Upon making the request via the API, you will get the latest version of the report, based on the current set of data in the reporting database.

This is already the behaviour when accessing the Impact Analysis and Recommendation Report through the Densify Console.

See Analysis: AWS Recommendations and Systems.

When working with ASGs that are hosting a Kubernetes clusters, the parent cluster name is returned, in both the /system and /subscriptions API resource response objects, and is stored in the attribute, "Kubernetes Cluster". This value was previously collected but not stored in an attribute and was not used.

See Working with Auto Scaling Groups in the Densify Online Help.

When using the standard API, Densify does not return an effortEstimate for systems that are ‘Not Analyzed’; however, when using the Subscription API Densify returns an effortEstimate of "Impossible" for systems that are ‘Not Analyzed’.

As a work-around, when enabling effortEstimate for the Subscription API Results, you need to add logic to trap and handle the effortEstimate for systems that are ‘Not Analyzed’.