CloudHealth is excited to announce the Public Beta of Custom Datasets.
Custom Datasets enable you to build highly personalized datasets using SQL queries. It significantly enhances Multi-Cloud reporting by allowing you to combine data from various providers, including AWS, Azure, and GCP, into a single, unified view.
You now have the flexibility to curate, join, or merge any dataset or datasets—whether it's a standard CloudHealth provided dataset or one you import via Data Connect—to create a new, public-facing dataset.
To begin exploring this capability, simply navigate to “Custom Datasets” in the left-hand menu. Learn more about Custom Datasets and how to get started building your own.
Two new columns have been added to the search results in the Asset Graph Explorer. Hourly Cost and Projected Monthly Cost. These are optional columns and must be added using the manage columns selection in the bottom left of the datagrid.
Hourly cost is calculated by taking the Total Effective Cost of a resource, and dividing it by the usage hours over the past 7 days. Projected Monthly Cost takes that hourly rate and calculates the full usage month of cost should the resource run with its current configuration for the entire month.
Some resources may not have cost. Because assets are collected at a higher frequency than billing data, there are cases where cost will be missing, usually if a resource has been created within the last 48 hours.
In addition to the new measures, all properties in the Asset Graph now have tooltips, these can be viewed by hovering over each property name in the datagrid. Sort for non-numeric columns is also now supported.
To support the changes that Google made to the billing export in January, we have made some major improvements to our cost categorizations. First, we have added support for all Committed Use Discount charges across all services.
In addition to these services, we also improved categorizations of non commitment charges, with a focus on AI services like Vertex AI, Cloud Dialogflow API, and Compute Engine! These should already be reflected in your Cost History and History Invoice reports.
GCP Cost Allocation by Resource Level Labels feature allows you to build Perspectives that reflect usage more accurately for your GCP Spend and usage. CloudHealth will now look for unique combinations of GCP labels and line item metadata and automatically construct assets for use in perspectives. This will allow the amount of assets that show in “Assets not Allocated” to be dramatically reduced.
This feature is on by default for all GCP customers. Learn more about GCP Cost Allocation by Resource Level Label.
Note: Enabling resource-level visibility requires configuring Detailed Data Export within your GCP console and selecting the corresponding detailed export table in your CloudHealth GCP Billing account settings. Changing a configuration from detailed export back to standard export is not recommended, as it will remove resource-level details and may break existing Perspectives.
CloudHealth now extends GCP Anomaly Detection to include Marketplace charges, giving you visibility into unexpected cost spikes across third-party services and subscriptions. Detect, classify, and act on anomalies beyond core GCP usage, before they impact your cloud spend.
The Smart Summary now offers an improved drill-down experience. Users can now click on the "Cost change" column to directly access the Smart Summary change reasons, automatically filtered by their selected Service Item. This enhancement allows for quick identification of significant cost changes and their underlying reasons without needing to reset filters. To support this functionality, "Service Item" has been added as a default column on the Smart Summary tab.
Furthermore, the default materiality filter of "Cost > $10" has been removed to enhance the drilling experience. Users can still set their own cost filters using the options in the report banner, where "Cost Change %" and "Smart Summary" have been added to assist in custom filtering.
CloudHealth has expanded Data Connect (Bring Your Own Data) beta capabilities to include Parquet file support alongside CSV. Parquet support allows you to ingest larger datasets more efficiently while maintaining flexibility in how external data is modeled and analyzed within CloudHealth.
Learn more and get started with Data Connect.
The next phase of Content Packages has been delivered! You can now create dashboards in the new experience and assign them to a content package. Once a dashboard has been added to a content package, all supporting reports will also be automatically added. This is a great opportunity to leverage all the work you’ve done with FlexReports and drive adoption of the New Experience.
Just like with publishing reports, you’ll have the option for changes made to either the dashboard, or reports assigned to that dashboard, to be applied automatically or require manual publishing.
We are updating our currency conversion provider. This change is operational in nature will not result in any measurable change to your CloudHealth reports or calculations, and no action is required from your side.
To reflect an organizational realignment, the platform is being rebranded from “Tanzu CloudHealth” to “CloudHealth”. You may notice updated branding across the login experience, URLs, email content, documentation references etc. This is a naming and branding update only and does not affect product capabilities.
NX Cost History
Enhanced Persistence: Y-axis and Category selections now persist when switching time granularities.
Improved Initialization: Corrected an issue where non-default X-axis selections were not initializing properly from query parameters.
Cleaned UI: Removed a redundant second "No Data" message from the chart area when no data is present.
Real-time Search: Datagrid search now applies results as you type, rather than requiring a click or pressing Enter.
NX Cost History Statements
Added ProductName column
Fixed sort to be case insensitive
Misc.
Fixed an issue in NX Cost History and Smart Summary where clicking the filter may attempt to scroll and then immediately close on Chrome browsers
Fixed a bug where filters weren’t respected after any X,Y,Z values were updated
Enhanced publish status tab in content package details page to lazy load outer and inner data in datagrid for better optimization
Resolved an issue where users were not able to check/uncheck “Select All” button in Policies add condition page
Fix double escape characters issue when SQL statements were copy-pasted to the editorsResolved an issue where double escape characters were incorrectly introduced when SQL statements were copied and pasted into the editors in New and Classic Interface