Why is the wrong BigQuery table name being populated in CH for GCP billing account?
search cancel

Why is the wrong BigQuery table name being populated in CH for GCP billing account?

book

Article ID: 284427

calendar_today

Updated On:

Products

CloudHealth

Issue/Introduction


This is likely due to expectations around seeing a resource level BQ table in CH, which is currently not supported.

Supported BQ table:  gcp_billing_export_v1_<billing_account_id>
Not supported in CH  >> gcp_billing_export_resource_v1_<billing_account_id>