Structure of CUD metadata export

This document provides reference information for the schema of Cloud Billing committed use discount (CUD) metadata that's exported daily to each table in BigQuery. This export provides a daily snapshot of your spend-based CUDs commitment metadata to a BigQuery table, which you can join with other billing data exports for better CUD management and reporting.

Ingress and egress rules

If you use VPC Service Controls for BigQuery resources on your project or organization, you must create ingress and egress rules to properly enable data exports to BigQuery.

Create an ingress rule that gives the individual access to create the export:

 - ingressFrom:
      identities:
      - PRINCIPAL_IDENTIFIER_OF_USER_INITIATING_EXPORT 
sources:
      - accessLevel: "*"
  ingressTo:
      roles:
      - roles/bigquery.dataOwner
      resources:
      - projects/ YOUR_PROJECT_ID_TO_HOST_EXPORT_DATA 
title: 'Ingress Rule Name'

See Principal identifiers for more information about principal identifier formats.

Create an egress rule to allow Google Cloud access to the BigQuery dataset through VPC Service Controls:

 - egressTo:
      roles:
      - roles/bigquery.dataOwner
      resources:
      - projects/132468967293
  egressFrom:
      identityType: ANY_IDENTITY
      sources:
      - accessLevel: "*"
      sourceRestriction: RESTRICTION_STATUS
  title: 'Egress Rule Name'

Schema of the CUD export data

In your BigQuery dataset, your Cloud Billing account CUD data is loaded into a data table named cud_subscriptions_export .

The following information describes the schema of the data that's exported to BigQuery.

`state`	String	The state of the commitment, for example `Active` or `Expired` .

Structure of CUD metadata export

Ingress and egress rules

Schema of the CUD export data

Related topics

Topics related to exported Cloud Billing data

Cost and pricing reports available in the Google Cloud console