Why are my GCP project totals higher in CloudHealth than in the GCP console?
search cancel

Why are my GCP project totals higher in CloudHealth than in the GCP console?

book

Article ID: 283530

calendar_today

Updated On: 10-23-2020

Products

CloudHealth

Issue/Introduction

This is most likely due to CloudHealth assigning Enterprise Support charges (and potentially other costs) to specific projects as opposed to GCP leaving them as generic costs not associated to any project. 

When referring to costs in the GCP platform and categorizing by "Project", there is a separate group of costs that will show as "Charges not specific to a project":

2020-02-12_1151.png

Enterprise Support charges will fall into this catch-all project category like the below example:

2020-02-12_1154.png

While these charges are not reflected in the project specific totals within the GCP platform, they are included in the project costs within CloudHealth.  CloudHealth will take the support cost value and divvy it up proportionally to the cost associated to each project. 

The best way to get cost values to match up at the project level is to filter out the "Support - Enterprise" charges in CloudHealth:

2020-02-12_1159.png

NOTE:  Enterprise Support charges are just an example of costs that fall into the "Charges not specific to a project" but GCP may include others.  Be sure to categorize those costs by SKU to get more detail into what charges fall into the "Charges not specific to a project" section as additional cost may need to be filtered out in CH for totals to match.