mirror of
https://github.com/open-metadata/OpenMetadata.git
synced 2025-08-15 20:46:58 +00:00
Docs: updating Cost Per TiB in docs (#21355)
Co-authored-by: Prajwal Pandit <prajwalpandit@Prajwals-MacBook-Air.local>
This commit is contained in:
parent
35d9f726ca
commit
cc96317f79
@ -145,6 +145,13 @@ In this field you need to specify the location/region in which the taxonomy was
|
||||
**Usage Location (Optional)**:
|
||||
Location used to query `INFORMATION_SCHEMA.JOBS_BY_PROJECT` to fetch usage data. You can pass multi-regions, such as `us` or `eu`, or your specific region such as `us-east1`. Australia and Asia multi-regions are not yet supported.
|
||||
|
||||
**Cost Per TiB (Optional)**:
|
||||
The cost (in USD) per tebibyte (TiB) of data processed during BigQuery usage analysis. This value is used to estimate query costs when analyzing usage metrics from `INFORMATION_SCHEMA.JOBS_BY_PROJECT`.
|
||||
|
||||
This setting does **not** affect actual billing—it is only used for internal reporting and visualization of estimated costs.
|
||||
|
||||
The default value, if not set, may assume the standard on-demand BigQuery pricing (e.g., $5.00 per TiB), but you should adjust it according to your organization's negotiated rates or flat-rate pricing model.
|
||||
|
||||
{% note %}
|
||||
If you want to use [ADC authentication](https://cloud.google.com/docs/authentication#adc) for BigQuery you can just leave
|
||||
the GCP credentials empty. This is why they are not marked as required.
|
||||
|
@ -131,6 +131,12 @@ In this field you need to specify the location/region in which the taxonomy was
|
||||
**Usage Location (Optional)**:
|
||||
Location used to query `INFORMATION_SCHEMA.JOBS_BY_PROJECT` to fetch usage data. You can pass multi-regions, such as `us` or `eu`, or your specific region such as `us-east1`. Australia and Asia multi-regions are not yet supported.
|
||||
|
||||
**Cost Per TiB (Optional)**:
|
||||
The cost (in USD) per tebibyte (TiB) of data processed during BigQuery usage analysis. This value is used to estimate query costs when analyzing usage metrics from `INFORMATION_SCHEMA.JOBS_BY_PROJECT`.
|
||||
|
||||
This setting does **not** affect actual billing—it is only used for internal reporting and visualization of estimated costs.
|
||||
|
||||
The default value, if not set, may assume the standard on-demand BigQuery pricing (e.g., $5.00 per TiB), but you should adjust it according to your organization's negotiated rates or flat-rate pricing model.
|
||||
|
||||
- If you prefer to pass the credentials file, you can do so as follows:
|
||||
```yaml
|
||||
|
@ -145,6 +145,13 @@ In this field you need to specify the location/region in which the taxonomy was
|
||||
**Usage Location (Optional)**:
|
||||
Location used to query `INFORMATION_SCHEMA.JOBS_BY_PROJECT` to fetch usage data. You can pass multi-regions, such as `us` or `eu`, or your specific region such as `us-east1`. Australia and Asia multi-regions are not yet supported.
|
||||
|
||||
**Cost Per TiB (Optional)**:
|
||||
The cost (in USD) per tebibyte (TiB) of data processed during BigQuery usage analysis. This value is used to estimate query costs when analyzing usage metrics from `INFORMATION_SCHEMA.JOBS_BY_PROJECT`.
|
||||
|
||||
This setting does **not** affect actual billing—it is only used for internal reporting and visualization of estimated costs.
|
||||
|
||||
The default value, if not set, may assume the standard on-demand BigQuery pricing (e.g., $5.00 per TiB), but you should adjust it according to your organization's negotiated rates or flat-rate pricing model.
|
||||
|
||||
{% note %}
|
||||
If you want to use [ADC authentication](https://cloud.google.com/docs/authentication#adc) for BigQuery you can just leave
|
||||
the GCP credentials empty. This is why they are not marked as required.
|
||||
|
@ -131,6 +131,12 @@ In this field you need to specify the location/region in which the taxonomy was
|
||||
**Usage Location (Optional)**:
|
||||
Location used to query `INFORMATION_SCHEMA.JOBS_BY_PROJECT` to fetch usage data. You can pass multi-regions, such as `us` or `eu`, or your specific region such as `us-east1`. Australia and Asia multi-regions are not yet supported.
|
||||
|
||||
**Cost Per TiB (Optional)**:
|
||||
The cost (in USD) per tebibyte (TiB) of data processed during BigQuery usage analysis. This value is used to estimate query costs when analyzing usage metrics from `INFORMATION_SCHEMA.JOBS_BY_PROJECT`.
|
||||
|
||||
This setting does **not** affect actual billing—it is only used for internal reporting and visualization of estimated costs.
|
||||
|
||||
The default value, if not set, may assume the standard on-demand BigQuery pricing (e.g., $5.00 per TiB), but you should adjust it according to your organization's negotiated rates or flat-rate pricing model.
|
||||
|
||||
- If you prefer to pass the credentials file, you can do so as follows:
|
||||
```yaml
|
||||
|
@ -176,6 +176,17 @@ Location used to query `INFORMATION_SCHEMA.JOBS_BY_PROJECT` to fetch usage data.
|
||||
Australia and Asia multi-regions are not yet supported.
|
||||
$$
|
||||
|
||||
$$section
|
||||
### Cost Per TiB $(id="costPerTB")
|
||||
|
||||
The cost (in USD) per tebibyte (TiB) of data processed during BigQuery usage analysis. This value is used to estimate query costs when analyzing usage metrics from `INFORMATION_SCHEMA.JOBS_BY_PROJECT`.
|
||||
|
||||
This setting does **not** affect actual billing—it is only used for internal reporting and visualization of estimated costs.
|
||||
|
||||
The default value, if not set, may assume the standard on-demand BigQuery pricing (e.g., $5.00 per TiB), but you should adjust it according to your organization's negotiated rates or flat-rate pricing model.
|
||||
|
||||
$$
|
||||
|
||||
$$section
|
||||
### Connection Options $(id="connectionOptions")
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user