Dashboard Updates (New Experience)

In order to support more layout controls within custom dashboards, we have introduced the following controls. 

Dashboard Column Override - By default all existing dashboards were 8 columns, limiting the number of widgets that could be evenly spaced within the same row. Customers can now override the column spacing on dashboards by opening Manage Dashboards → Dashboard Settings → Change the layout to 6 or 12. All new custom dashboards will have a default layout of 12 columns, existing dashboards must be changed manually. 

Reduce Minimum Widget Container Size - Custom Report widgets have had their minimum size dramatically reduced, dragging the widget from the bottom and top corners will now properly resize as square

Chart Dynamic Vertical Sizing - Charts in custom report widgets will now scale vertically to remove white space on large widgets

Widget Legend Count - Customers can now set the number of entries in the legend from 5-25 per widget. The default is 10 entries. 

Provider Filter Changes - The Provider filter that automatically gets copied to custom dashboards has been removed, dashboard filters will be supported in the future. 

GCP Kubernetes Cost History Dataset (New Experience)

CloudHealth now supports GKE cost and usage reporting through the GKE standard dataset. Customers can now build custom GKE reports using this dataset by selecting it in the custom report dropdown. An out of the box GKE Cost History report will be added in a future release. In order to see these data, customers must have the detailed billing export enabled in Google Cloud.

AWS Database Savings Plan Recommendations (New Experience)

CloudHealth now supports the newly launched AWS Database Savings Plans within its optimization suite, extending beyond existing Compute Savings Plan recommendations. These AWS-native recommendations are seamlessly surfaced in the CloudHealth platform, enriched with enhanced visibility into key metrics such as coverage, utilization, expiration, and overall Effective Savings Rate.

In the new CloudHealth experience, both AWS and Azure Savings Plans are unified within a single view, enabling organizations to evaluate commitment opportunities across clouds and prioritize actions based on highest return on investment (ROI). To access this capability, navigate to: CloudHealth New Experience > Recommendations > Commitment Discounts > Spend-Based Opportunities. For additional details, refer to the associated Help Center article.

Note: New IAM role permissions are required in order for CloudHealth to successfully retrieve AWS Database Savings Plan Recommendations. See the Help Center article for more details.

{ "Statement": [ { "Effect": "Allow", "Action": [ "ce:GetSavingsPlansPurchaseRecommendation", "ce:GetSavingsPlanPurchaseRecommendationDetails", "ce:ListSavingsPlansPurchaseRecommendationGeneration", "ce:StartSavingsPlansPurchaseRecommendationGeneration" ], "Resource": "*" } ] }

General Availability | Azure Rightsizing Recommendations  (New Experience)

CloudHealth announces the availability of Azure rightsizing recommendations across a broad set of services, including Virtual Machines, Disks, Virtual Machine Scale Sets, Kubernetes Service, Databricks Workspaces, Cosmos DB, Data Factory, Data Explorer, Log Analytics Workspaces, Front Door, and App Services.

Recommendations are categorized as Terminate, Downsize, Autoscale, or Optimize Configuration, depending on the service. As part of general availability, we have made the following enhancements to Azure Rightsizing capability. 

• Perspective Support: Azure Rightsizing recommendations now can be grouped/filtered based on specific perspective and perspective groups. ‘Region’ is also available as a filter. 

• Service Specific Additional Columns: Rightsizing recommendations are augmented with additional metadata specific to service (e.g. for Azure Virtual Machines recommendations we provide P95 metrics for CPU, Memory and Storage)

• Feedback on Recommendations: Azure Rightsizing Recommendations status (Active, Snoozed, Suppressed) is included along with recommendations.

For additional details, refer to the associated Help Center article.

AWS Billing Transfer Support (New Experience)

CloudHealth now supports AWS Billing Transfer through Data Connect for both direct customers and partners. Within Billing Transfer, consolidated families can be configured to deliver their AWS Cost and Usage Reports (CURs) to a centralized S3 bucket. Through Data Connect, CloudHealth can collect CURs for consolidated accounts even when the source accounts differ from the account hosting the S3 bucket.

To support customers with both historical and post-migration data, Data Connect also includes the configuration of multiple CUR bucket locations for a single AWS consolidated family. CloudHealth can then collect CURs generated before and after a Billing Transfer, even if they reside in different S3 buckets, accounts, or require separate access credentials.

This is currently possible through API. The general documentation can be found here and the API documentation can be found here

For more information on AWS Billing Transfer see the AWS Documentation.

Coming Soon | New Role Permission for Forecasting

We are now introducing a specific granular permissions to govern access to Forecasting. This change will not impact standard roles. However, for customers who have created custom roles, users assigned to those roles will no longer have access to Forecasting by default and will need to be explicitly granted access. Read, Update and Export permissions need to be explicitly assigned to required users. 

For any queries or assistance with enabling Forecasting permissions, please contact your Technical Account Manager.

UI Changes, Updates, and Fixes

Bug Fixes

• Resolved an issue where charts were misleadingly interpreted as having no data because small bar values were not visible.