FAST: add instructions for billing export to stage 0 README (#1051)
* Readme updated with Billing data export API Limitations Because of the billing API limitations, Though BigQuery dataset will be created within billing project, it will be empty. BigQuery export have to be manually enabled in order for the data to be populated within the dataset. Since the Readme doesn't capture this, a note and reference link was added. * fix typos Co-authored-by: Ludovico Magnocavallo <ludo@qix.it>
This commit is contained in:
parent
5a9dc822dc
commit
c297d1061f
|
@ -54,6 +54,8 @@ For same-organization billing, we configure a custom organization role that can
|
|||
|
||||
For details on configuring the different billing account modes, refer to the [How to run this stage](#how-to-run-this-stage) section below.
|
||||
|
||||
Because of limitations of API availability, manual steps have to be followed to enable billing export within billing project to BigQuery dataset `billing_export` which will be created as part of the bootstrap stage. THe process to share billing data [is outlined here](https://cloud.google.com/billing/docs/how-to/export-data-bigquery-setup#enable-bq-export).
|
||||
|
||||
### Organization-level logging
|
||||
|
||||
We create organization-level log sinks early in the bootstrap process to ensure a proper audit trail is in place from the very beginning. By default, we provide log filters to capture [Cloud Audit Logs](https://cloud.google.com/logging/docs/audit) and [VPC Service Controls violations](https://cloud.google.com/vpc-service-controls/docs/troubleshooting#vpc-sc-errors) into a Bigquery dataset in the top-level audit project.
|
||||
|
|
Loading…
Reference in New Issue