Locale selector icon
Jan202411

Azure SQL DB Rightsizing – General Availability

We are pleased to announce the general availability of our Azure SQL Database Rightsizing tool. Part of the Azure SQL family, Azure SQL DB is an always-up-to-date, fully managed relational database service built for the cloud.  

Our new Azure SQL DB rightsizing feature generates recommendations to move to a cheaper database type based on your current usage characteristics. This feature supports both database transaction unit (DTU) and vCore purchase models. With an enhanced user interface, this feature delivers: 

  • Recommendations for both DTU and vCore based databases 

  • Cost and savings summaries 

  • Customizable efficiency targets 

  • Ability to drill down into each recommendation to view usage and see up to 3 alternative options 

For more information, please read the documentation.

AWS S3 Rightsizing – Public Beta

We are pleased to announce the public beta of our AWS S3 Rightsizing tool. Simple Storage Service (S3) is a popular cloud object storage service used for common enterprise storage needs such as images, videos, website content, backups, and file sharing. 

AWS S3 Rightsizing offers insights and visibility into critical bucket-level attributes and metrics, providing optimization recommendations to move to cheaper, more relevant bucket types based on your usage characteristics. Complete with a new user interface, this feature delivers: 

  • Cost and savings summaries

  • Relevant informative details for each bucket being used

  • Ability to drill down into each recommendation to view usage metrics and see up to 3 alternative options

Recommendations are at the bucket level and consider bucket size & usage characteristics, allowing users to consume recommendations and actions based on the object's needs and impact. For more information, please read the documentation.

Bring Your Own Data (BYOD) – Private Beta

We are excited to announce the private beta for the Bring Your Own Data (BYOD) capability. This feature gives you the ability to:

  • Bring “any data” into the Tanzu CloudHealth platform as a dataset by posting the data file into a storage location that you own. For the private beta, you will need to provide the data in a specific standard format. In the future, data with “custom” format will be supported.

  • Augment the cloud data available in our platform with data brought in through BYOD. You can slice-and-dice, visualize, and combine this data with other standard cloud datasets, leveraging the FlexReports framework.

We’re currently opening this feature to a limited set of private beta customers to complete validation and testing. If you’re interested in participating, please contact your Technical Account Manager to determine eligibility.

Updates to the Kubernetes Overview Report

This week we are announcing major enhancements to the Kubernetes Overview Report. The following updates are included in this announcement:

  • The data source for the Kubernetes overview report is changing from the Classic Kubernetes Reports to the new Kubernetes FlexReports. 

  • The data in this report is now aggregated over 30 days, which is an increase from the previous 14 day aggregation period.

  • Added support for Kubernetes Workloads which now includes Deployments, Daemonsets, StatefulSets, ReplicaSets, and Jobs.

Deprecation of AWS ECS Support – Coming Soon

The AWS Elastic Container Service (ECS) Reports and the associated Container Cost History functionality for ECS will be discontinued on January 25, 2024. Existing users of these reports will continue to have access to them till one year from the date of deprecation. The Reports impacted are:

  • ECS Resources

  • ECS Allocation

  • Container Cost History (ECS functionality only - all other report functionality will not be impacted)

Please contact your Technical Account Manager for more information. 

Update Regarding AWS CUR 2.0 – No Action Required

Back in November, AWS announced support for a new type of CUR export called “CUR 2.0”. This new format contains the same data but adds minor improvements that Tanzu CloudHealth is currently already solving using APIs. As of now, CloudHealth does not support the new format, so no action is required. If configuring new CURs, you must select the “Legacy CUR Export” option. If you are looking to test the new format, please export this data to a different S3 bucket than the one configured in CloudHealth.