vRealize Operations Integration for CloudHealth – General Availability

We’re excited to announce the general availability of the VMware vRealize Operations integration for CloudHealth! With the public beta we announced support for vRealize Operations on-premises, and now we are announcing support for vRealize Operations Cloud as well.

You can enable the management pack by accessing ‘marketplace’ under Administration and enable ‘vRealize Operations Integration for CloudHealth management pack.’ To connect to your existing vRealize Operation on-premises instance(s), you can download the management pack from VMware Marketplace and go ahead with the deployment. All your vCenter accounts will be automatically synchronized with CloudHealth to provide cost, usage, and asset visibility into your vSphere-based infrastructure.

Learn more about the vRealize Operations integration for CloudHealth in this Help Center Article and Knowledge Base FAQ.

Automated Identification of Deleted Projects in GCP – Now Available

To improve visibility into your active GCP projects, we have introduced two new project health statuses: Pending Deletion and Deleted. After a project is deleted through the Google console, it goes into a pending state for 30 days in GCP. (See Google documentation on deleting projects for more details.) Within four hours of that happening, CloudHealth will update the health status of that project to Pending Deletion and we will deactivate all resources for that project.

After 32 days of not seeing any cost line items in the BigQuery export (including $0.00 lines), CloudHealth will automatically set the state of that project to Deleted and that project will no longer show up on the projects page by default. You will still be able to filter projects based on health status. These changes will have no impact to the cost reports; All projects with costs will continue to show up.

The projects graphQL API will now have two additional values in the ‘healthStatus’ field: PENDING_DELETION and DELETED, indicating which state the project is in currently.

You can also set policies to generate an alert when projects are in a Pending Deletion or Deleted state. More importantly, a policy alerting you of ‘Critical’ projects will become more meaningful, as deleted projects will no longer be returning false alerts.

New GCP Product Categories

We have added support for categorizing costs on the cost reports for the following GCP services: Cloud Domain, Elastic Cloud (managed Elasticsearch Service), Pub/Sub Lite.

All Reservations Asset Report in Azure

We have released a new asset report in Azure to report on the inventory of your reservations for all services. You can now go to this single report to view your inventory of reservations for services like VMs, PostgreSQL, and Databricks. We will be releasing additional improvements in the coming weeks, such as Perspective support, advanced filtering, and policy support. Once complete, we will be deprecating the existing VM Reservation Order Asset Report in favor of this All Services report. You do not need to make any updates to your existing permissions to use this feature.

Pagination in Filters for Categories with Many Values

Several of our customers have reporting categories in CloudHealth with many values. Common dimensions with many values include S3 buckets, Accounts, and Kubernetes Namespaces, to name a few. We’ve improved the user experience by adding pagination to interactive reporting filters. When a category has more than 50 values, we will paginate the filter options. Search works across all pages for that category, and the “Select All” function selects everything in scope of the search for that category.

Updates to FlexReports: More SQL Functions and GraphQL API Change

We’ve added support for two more SQL functions in FlexReports: TRIM and COALESCE.

We've also added support for conditional aggregation. This should help in achieving pivoting use cases on the datasets. You can find the complete list of supported functions and examples here.

In ‘createFlexReport’ mutation, the deprecated input field ‘datasource’ is now removed. Please use the field ‘dataset’ to pass the value. This change requires you to update your scripts to ‘createFlexReport.’

New mutation ‘executeFlexReport’ can be used to trigger a FlexReport on demand; You no longer need to use ‘updateFlexReport.’