GCP Assets suddenly assigned to Assets Not Allocated in Cost History report
search cancel

GCP Assets suddenly assigned to Assets Not Allocated in Cost History report

book

Article ID: 426474

calendar_today

Updated On:

Products

CloudHealth

Issue/Introduction

When filtering by your perspective in the Cost History report, you many notice that many GCP assets are unexpectedly showing up in Assets Not Allocated.

Resolution

This is likely happening because of our CARLL (Cost Allocation by Resource Level Label) feature. The feature is now by default enabled for all customers. It was discovered that when an asset is already assigned to at least one perspective in a customer tenant our Account Fallback Logic will fail when CARLL is enabled.  Our Account Fallback Logic is designed to check to see if there are any assets which are NOT allocated to any perspectives. If an asset meets this criteria, we then check to see if the project associated with the asset is assigned to a group in a perspective. If it is, then we go ahead and allocate the cost for that asset to the same group in the perspective. However with CARLL enabled this Account Fallback Logic can fail, if the asset is already allocated to any other perspective or group in your tenant.
This is what is happening when you categorize by your Cost Center perspective in the Cost History report. 

If you are experiencing this issue please reach out to CloudHealth support.