Total costs between CloudHealth and AWS Cost Explorer are not matching due to CUR time interval

Products

• CloudHealth

Issue/Introduction

CloudHealth requires the CUR time granularity be set to "Hourly" in order to be properly aligned with AWS cost explorer.

Resolution

The CloudHealth platform expects and requires all CUR files be set to the "Hourly" time ganularity as outlined in our documentation here https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/cloudhealth/saas/index/getting-started-with-tanzu-cloudhealth-getting-started-index/getting-started-with-tanzu-cloudhealth-aws-quick-start.html

Additional Information

You can confirm your CUR time granularity through the following two methods.

Method 1: This is the most reliable way to verify if a report is configured as an "AWS Export."

1. Log in to the AWS Billing and Cost Management console.
2. In the left-hand navigation pane, look for Data Exports.
-Note: If you don't see this, look under "Legacy Pages" for Cost & Usage Reports.You will see a list of exports.

3. Click on the Export Name you want to check.
4. In the Export details or Report details section, look for a field labeled Time granularity.
-It will show one of three values: Hourly, Daily, or Monthly.

Method 2: If you are looking for an automated way to detect if a report is an "AWS Export" (as mentioned in your logic), you can query the API.

For Legacy CUR Reports: Run this command to see all official CUR definitions and their granularity:

aws cur describe-report-definitions

In the JSON output, look for the "time_unit" key. It will be HOURLY, DAILY, or MONTHLY. Remember, for Cloudhealth we require HOURLY: