You can now view granular AlloyDB for PostgreSQL usage in the Cloud Billing Detailed export to BigQuery
Share
Services
## Feature
**You can now view granular AlloyDB for PostgreSQL usage in the Cloud Billing Detailed export to BigQuery**
You can now view granular **AlloyDB for PostgreSQL** _cluster_, _instance_, and _backup data_ in the Google Cloud Billing detailed export. Use the `resource.global_name` and `resource.name` fields in the export to view and filter your detailed AlloyDB cluster, instance, and backup usage.
[Review the schema of the Detailed cost data export](https://cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/detailed-usage).
## Feature
**Tags data for AlloyDB for PostgreSQL cluster, instance, and backup usage is available in both the [_Standard usage cost export_](https://cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/standard-usage) and the [_Detailed usage cost export_](https://cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/detailed-usage).**
To learn more about Tags, see [Tags overview](https://cloud.google.com/resource-manager/docs/tags/tags-overview). To learn about using Tags in your cost data exported to BigQuery, see [about tags](https://cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/standard-usage#tags) and [query examples with tags](https://cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/standard-usage#query-with-tags).
What else is happening at Google Cloud Platform?
The CPU allocation setting has been renamed to Billing in the Google Cloud console for Cloud Run services
December 13th, 2024
Services
Share
Google Kubernetes Engine (GKE) - December 13th, 2024 [Feature]
December 13th, 2024
Services
Share