Partner | Support for Client API ID for GraphQL APIs

We have released support for using the Client API ID to get the GraphQL API tokens for your customers! Still in CRN format, you can now use the Client API ID instead of the customer ID to get the customer level authentication tokens. With these tokens, you’ll be able to use all our GraphQL APIs in the context of the partner customer's tenant. 

Note, the current workflow using the Customer ID is still supported; this is an alternate way to get the customer-specific API tokens. 

Updates to Reservation Apportioning in AWS Partner Billing – Now Available

We have released support for apportioning for all reservable services through AWS Partner Billing! Like with Savings Plans and EC2 Reserved Instances, you will now see those costs show up in the Cost History Report throughout the month, instead of just on the start date when looking at the daily interval. 

vRealize Operations Integration for CloudHealth – Public Beta 

We’re excited to announce the integration of vRealize Operations and CloudHealth, available as a public beta! Previously, to get visibility into cost, usage, and inventory for datacenter you would have to add vCenter accounts into the CloudHealth Hybrid module and deploy the CloudHealth Aggregator for collection from these vCenter accounts. Now, you can connect to your existing vRealize Operations Instance(s) directly. All your vCenter accounts which are already added in one or more vRealize Operations Instances will be automatically synchronized with CloudHealth, leveraging the “vRealize Operations Integration for CloudHealth” management pack, to provide visibility into your vSphere-based infrastructure. You can download the management pack from this S3 location for the public beta.  

For existing CloudHealth Hybrid customers, you will have the option to continue using our CloudHealth Hybrid module for data center (with explicit vCenter collection and aggregator deployment) or you may choose to leverage the vRealize Operations integration for CloudHealth (with the management pack deployment). If you would like to connect to your existing vRealize Operations instances, all the vCenter accounts need to be already added to vRealize Operations. The archived cost data for the prior months in CloudHealth will be preserved. This management pack will be compatible with vRealize Operations version 8.2 and above. This integration will work only for vRealize Operations on-premises instances for public beta. Support for vRealize Operations Cloud instances will be supported with general availability.  

Learn more about the vRealize Operations Integration for CloudHealth in this Help Center Article. 

Deprecation of GCP Billing CSV Reports - Coming Soon 

We will be officially deprecating all support for Billing CSVs on July 30th. This includes the Cost History, Compute Engine, and Billing Statements reports. On this date, we will stop collecting costs from Billing CSVs and will rely solely on the BigQuery Billing Exports. These reports will not have any data after July 30th, but they will continue to be available in the navigation for some time. If you have not done so, please update your configuration in CloudHealth to use the BigQuery billing export as outlined in this Help Center article. 

Automated Identification of GCP Deleted Projects – Coming Soon 

To improve visibility into your active GCP projects, we’re introducing two new project health status’ in the coming weeks: 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 their 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’ll still be able to use the filter to view all projects based on health status. These changes will have no impact to the cost reports, all projects with costs will continue to show up. 

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. 

Once deployed, the projects page will only report on active projects by default. We will go through historical costs and set the projects to “Deleted” if we have not seen costs for 32 days. 

Update to Azure Multi-Currency Handling – VM RI Optimizer 

The way cloud providers localize billing information to local currencies can vary not only across cloud providers, but also over time as they evolve their approaches. As Azure now charges centrally in a normalized currency (USD) and converting to currency is a secondary step, CloudHealth has adapted accordingly. For the CloudHealth VM RI Optimizer, an optimization tool for pricing hypothetical scenarios to help you decide the most optimal RI purchase for your VMs, CloudHealth is now doing its own conversion of those costs according to the latest exchange rate (from the end of the previous day). This exchange rate is applied when an RI quote snapshot is generated, so if you need to capture the latest currency fluctuations, we recommend generating a new quote. Customers in non-USD regions will now experience a more accurate and complete experience from the VM RI Optimizer.