bigquery-observability

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

BigQuery Observability

BigQuery 可观测性

Tool Selection

工具选择

Tool	Primary Use Cases	Strengths & Capabilities	When to Avoid / Limitations
`INFORMATION_SCHEMA` ( `I_S` )	Historical analysis, cohort comparison ( `normalized_literals` ), discovery of fast/slow windows, reservation/project timelines, multi-job aggregates, cost/billing tracing.	Flexible SQL querying across `JOBS` , `JOBS_TIMELINE` , and `RESERVATIONS` ; supports custom time windows and grouping.	Avoid for high-frequency real-time polling or single-job point-lookups (can consume slots and take seconds to execute).
REST API ( `jobs.api` / `reservation.api` )	Single-job point-lookup, real-time stage bottleneck diagnosis, automated pipeline status checks, reservation/capacity commitment configuration inspection ( `reservations.get` , `reservations.list` ).	Zero-SQL overhead, fast REST/CLI point-lookups ( `bq show -j` , `bq show --reservation` ), instant access to `performanceInsights` , `queryPlan` , and structural metadata.	Avoid for aggregate analysis across thousands of jobs, cross-project historical comparison, or system timeline aggregations.
`Cloud Monitoring` (Monarch / Charts)	Real-time alerting, fleet-wide dashboards, continuous slot utilization tracking, high-level SLA/SLO monitoring.	Out-of-the-box charts for slot utilization, query throughput, `PENDING` queue depth, and execution latency; low-latency alerting without running queries.	Avoid for SQL-level debugging, individual query text inspection, or stage-level execution detail.

工具	主要用例	优势与功能	避免使用场景/限制
`INFORMATION_SCHEMA` ( `I_S` )	历史分析、队列比较（ `normalized_literals` ）、快慢窗口发现、预留/项目时间线、多作业聚合、成本/账单追踪。	支持跨 `JOBS` 、 `JOBS_TIMELINE` 和 `RESERVATIONS` 的灵活SQL查询；支持自定义时间窗口和分组。	避免用于高频实时轮询或单作业点查询（会消耗槽位，执行可能需要数秒）。
REST API ( `jobs.api` / `reservation.api` )	单作业点查询、实时阶段瓶颈诊断、自动化管道状态检查、预留/容量承诺配置检查（ `reservations.get` 、 `reservations.list` ）。	零SQL开销，快速REST/CLI点查询（ `bq show -j` 、 `bq show --reservation` ），可即时访问 `performanceInsights` 、 `queryPlan` 和结构化元数据。	避免用于跨数千个作业的聚合分析、跨项目历史比较或系统时间线聚合。
`Cloud Monitoring` (Monarch / Charts)	实时告警、全集群仪表盘、持续槽位利用率跟踪、高层级SLA/SLO监控。	开箱即用的槽位利用率、查询吞吐量、 `PENDING` 队列深度和执行延迟图表；无需运行查询即可实现低延迟告警。	避免用于SQL级调试、单个查询文本检查或阶段级执行详情分析。

Prerequisites & Environment Setup

前提条件与环境设置

Before retrieving telemetry or running observability queries, ensure the Google Cloud environment and project are configured:

Google Cloud SDK: Ensure the Google Cloud SDK is installed and configured.
Project Selection: Set the active Google Cloud project:
bash
```
gcloud config set project {project_id}
```
API Enablement: Ensure the BigQuery and Cloud Monitoring APIs are enabled:
bash
```
gcloud services enable bigquery.googleapis.com monitoring.googleapis.com
```
Authentication: Authenticate the environment:
- CLI queries and
```
bq
```
  commands:
```
gcloud auth login
```
- SDKs and automated client tools:
```
gcloud auth application-default login
```
- Service accounts: Set
```
GOOGLE_APPLICATION_CREDENTIALS="/path/to/key.json"
```
Billing & IAM Roles:
- Verify an active Google Cloud Billing account is attached to
```
{project_id}
```
  .
- Ensure appropriate IAM roles:
  - ```
  roles/bigquery.jobUser
```
  : Running telemetry queries.
- ```
roles/bigquery.resourceViewer
```
    or
```
roles/bigquery.admin
```
    : Organization-level jobs and reservation telemetry.
  - ```
  roles/monitoring.viewer
```
  : Cloud Monitoring metrics.

在检索遥测数据或运行可观测性查询之前，请确保Google Cloud环境和项目已配置完成：

Google Cloud SDK：确保已安装并配置Google Cloud SDK。
项目选择：设置当前活跃的Google Cloud项目：
bash
```
gcloud config set project {project_id}
```

API启用：确保已启用BigQuery和Cloud Monitoring API：

bash

gcloud services enable bigquery.googleapis.com monitoring.googleapis.com

身份认证：为环境进行身份认证：
- CLI查询和
```
bq
```
  命令：
```
gcloud auth login
```
- SDK和自动化客户端工具：
```
gcloud auth application-default login
```
- 服务账号：设置
```
GOOGLE_APPLICATION_CREDENTIALS="/path/to/key.json"
```
计费与IAM角色：
- 确认
```
{project_id}
```
  已绑定有效的Google Cloud计费账号。
- 确保拥有适当的IAM角色：
  - ```
  roles/bigquery.jobUser
```
  ：运行遥测查询。
- ```
roles/bigquery.resourceViewer
```
    或
```
roles/bigquery.admin
```
    ：组织级作业和预留遥测。
  - ```
  roles/monitoring.viewer
```
  ：查看Cloud Monitoring指标。

Workflow

工作流

Single-Job Point-Lookup (Zero-SQL Overhead): For single-job slowness or inspection, always prioritize the REST API or CLI (
```
bq show -j
```
) first. It provides zero-SQL overhead and fast point-lookups for internal stage bottlenecks (
```
performanceInsights
```
,
```
queryPlan
```
, shuffle spill).
bash
```
bq show --location={location} -j {project_id}:{job_id}
```
Diagnostic Transition Logic: If no job-level issues are found (e.g. no clear internal bottlenecks), the investigation should transition to system-level
```
INFORMATION_SCHEMA
```
queries (such as
```
JOBS_TIMELINE
```
or
```
RESERVATIONS_TIMELINE
```
) to check for broader issues like slot contention, queueing delay, or noisy neighbors.

单作业点查询（零SQL开销）： 对于单作业变慢或检查场景，始终优先使用REST API或CLI（
```
bq show -j
```
）。它提供零SQL开销的快速点查询，可定位内部阶段瓶颈（
```
performanceInsights
```
、
```
queryPlan
```
、shuffle溢出）。
bash
```
bq show --location={location} -j {project_id}:{job_id}
```
诊断转换逻辑： 如果未发现作业级问题（例如没有明确的内部瓶颈），应将调查转向系统级
```
INFORMATION_SCHEMA
```
查询（例如
```
JOBS_TIMELINE
```
或
```
RESERVATIONS_TIMELINE
```
），以检查更广泛的问题，如槽位争用、排队延迟或噪声邻居。

Best Practices for Writing

INFORMATION_SCHEMA

Queries

编写

INFORMATION_SCHEMA

查询的最佳实践

Every query against a BigQuery

INFORMATION_SCHEMA

view must be qualified with either a region qualifier or a dataset qualifier, optionally prefixed by a project qualifier.

针对BigQuery

INFORMATION_SCHEMA

视图的每个查询都必须使用区域限定符或数据集限定符进行限定，可选择添加项目限定符作为前缀。

Qualification Syntax & Scope Matching

限定语法与范围匹配

Region-Qualified Syntax:

googlesql

`{project_id}`.`region-{region}`.INFORMATION_SCHEMA.{view}

Example:

 `my-project`.`region-us`.INFORMATION_SCHEMA.JOBS

Applies to: Regional telemetry views (

JOBS*

JOBS_TIMELINE*

RESERVATIONS*

CAPACITY_COMMITMENTS*

TABLE_STORAGE*

STREAMING_TIMELINE*

). The client query execution location MUST match the

region-{region}

qualifier (or BigQuery throws:

Not found: Table {project_id}:region-{region}.INFORMATION_SCHEMA.{view} was not found in location {location}

Dataset-Qualified Syntax:

googlesql

`{project_id}`.`{dataset_id}`.INFORMATION_SCHEMA.{view}

Example:

 `my-project`.`analytics`.INFORMATION_SCHEMA.TABLES

Applies to: Dataset-scoped views (

PARTITIONS

SEARCH_INDEXES*

ROW_ACCESS_POLICIES

). Never use

region-

with dataset views.

Dual-Scoped Views: Views like
```
TABLES
```
,
```
COLUMNS
```
,
```
COLUMN_FIELD_PATHS
```
,
```
VIEWS
```
,
```
ROUTINES
```
, and
```
VECTOR_INDEXES
```
can be qualified with either
```
{dataset_id}
```
or
```
region-{region}
```
depending on whether dataset or region-wide analysis is required.
Project Qualifier (
{project_id}
): Optional. If omitted, queries default to the project in which the query is executing. Specifying a project qualifier on organization-level views (e.g.
```
JOBS_BY_ORGANIZATION
```
) has no impact on results.

区域限定语法：

googlesql

`{project_id}`.`region-{region}`.INFORMATION_SCHEMA.{view}

示例：

 `my-project`.`region-us`.INFORMATION_SCHEMA.JOBS

适用范围： 区域级遥测视图（

JOBS*

、

JOBS_TIMELINE*

、

RESERVATIONS*

、

CAPACITY_COMMITMENTS*

、

TABLE_STORAGE*

、

STREAMING_TIMELINE*

）。客户端查询执行位置必须与

region-{region}

限定符匹配（否则BigQuery会报错：

Not found: Table {project_id}:region-{region}.INFORMATION_SCHEMA.{view} was not found in location {location}

）。

数据集限定语法：

googlesql

`{project_id}`.`{dataset_id}`.INFORMATION_SCHEMA.{view}

示例：

 `my-project`.`analytics`.INFORMATION_SCHEMA.TABLES

适用范围： 数据集级视图（

PARTITIONS

、

SEARCH_INDEXES*

、

ROW_ACCESS_POLICIES

）。数据集视图切勿使用

region-

前缀。

双范围视图： 像
```
TABLES
```
、
```
COLUMNS
```
、
```
COLUMN_FIELD_PATHS
```
、
```
VIEWS
```
、
```
ROUTINES
```
和
```
VECTOR_INDEXES
```
这类视图，可以根据需要使用
```
{dataset_id}
```
或
```
region-{region}
```
进行限定，分别对应数据集级或区域级分析。
项目限定符（
{project_id}
）：可选。如果省略，查询默认使用当前执行查询的项目。对组织级视图（例如
```
JOBS_BY_ORGANIZATION
```
）指定项目限定符不会影响查询结果。

Principle of Least Privilege & Scope Selection

最小权限原则与范围选择

When constructing

INFORMATION_SCHEMA

queries, always select the scope and view variant with the least IAM permission requirement that satisfies the analytical need:

User-Level over Project-Level (
_BY_USER
): When diagnosing queries or sessions executed by the current user, use
```
_BY_USER
```
(e.g.
```
JOBS_BY_USER
```
,
```
SESSIONS_BY_USER
```
). This requires only
```
bigquery.jobs.list
```
(granted via
```
roles/bigquery.user
```
or
```
roles/bigquery.jobUser
```
), avoiding the need for
```
bigquery.jobs.listAll
```
or
```
roles/bigquery.admin
```
.
Dataset-Level over Region/Project-Level: When querying table metadata, columns, or views for a specific dataset, qualify with
```
{dataset_id}
```
rather than
```
region-{region}
```
when project-level metadata access is restricted. Dataset-scoped queries require permissions only on that target dataset.
Project-Level over Org/Folder-Level (
_BY_PROJECT
): Always start with project-scoped views before escalating to
```
_BY_FOLDER
```
or
```
_BY_ORGANIZATION
```
. Folder and organization queries require broad folder/org IAM permissions (
```
bigquery.jobs.listAll
```
or
```
bigquery.tables.list
```
at the Org/Folder node).

Metadata Roles over Data Roles: For table and storage introspection, prefer

roles/bigquery.metadataViewer

(which provides

bigquery.tables.get

and

bigquery.tables.list

) over

roles/bigquery.dataViewer

roles/bigquery.dataOwner

when data read access (

bigquery.tables.getData

) is not needed. (Note:

INFORMATION_SCHEMA.PARTITIONS

uniquely requires

bigquery.tables.getData

构建

INFORMATION_SCHEMA

查询时，始终选择满足分析需求所需IAM权限最少的范围和视图变体：

用户级优先于项目级（
_BY_USER
）：诊断当前用户执行的查询或会话时，使用
```
_BY_USER
```
后缀的视图（例如
```
JOBS_BY_USER
```
、
```
SESSIONS_BY_USER
```
）。这仅需要
```
bigquery.jobs.list
```
权限（通过
```
roles/bigquery.user
```
或
```
roles/bigquery.jobUser
```
授予），无需
```
bigquery.jobs.listAll
```
或
```
roles/bigquery.admin
```
权限。
数据集级优先于区域/项目级： 查询特定数据集的表元数据、列或视图时，如果项目级元数据访问受限，请使用
```
{dataset_id}
```
限定而非
```
region-{region}
```
。数据集级查询仅需要目标数据集上的权限。
项目级优先于组织/文件夹级（
_BY_PROJECT
）：始终先从项目级视图开始，再升级到
```
_BY_FOLDER
```
或
```
_BY_ORGANIZATION
```
级视图。文件夹和组织级查询需要广泛的文件夹/组织IAM权限（组织/文件夹节点上的
```
bigquery.jobs.listAll
```
或
```
bigquery.tables.list
```
权限）。
元数据角色优先于数据角色： 对于表和存储内省操作，优先选择
```
roles/bigquery.metadataViewer
```
（提供
```
bigquery.tables.get
```
和
```
bigquery.tables.list
```
权限）而非
```
roles/bigquery.dataViewer
```
或
```
roles/bigquery.dataOwner
```
，前提是不需要数据读取权限（
```
bigquery.tables.getData
```
）。（注意：
```
INFORMATION_SCHEMA.PARTITIONS
```
是个例外，它需要
```
bigquery.tables.getData
```
权限。）

Execution Guardrails & Query Invariants

执行防护与查询不变式

Mandatory Partition & Time Filtering: Always filter on
```
creation_time
```
(e.g.,
```
creation_time >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 3 DAY)
```
) or
```
usage_date
```
to avoid full metadata table scans.
Script Wrapper Exclusion: Add
```
AND (statement_type != 'SCRIPT' OR statement_type IS NULL)
```
when aggregating compute spend to avoid double-counting parent scripts and child jobs.
Column Pruning: Never use
```
SELECT *
```
against
```
INFORMATION_SCHEMA
```
; only project required columns.
Dry Run & Cost Estimation: Use a dry run (
```
bq query --dry_run --use_legacy_sql=false "{query}"
```
or API
```
dryRun=true
```
) before executing complex queries, multi-view joins, or large scans to validate syntax and estimate
```
totalBytesProcessed
```
at zero cost.
Empty Regional Scope (0 Rows): If the execution location matches the qualifier, but the project has no datasets or jobs in that region, the query succeeds and returns 0 rows. Never assume 0 rows means 0 usage—always verify the target dataset locations.
Non-Hierarchical Region Scope: Region qualifiers are not hierarchical. Multi-regions do not encompass single regions (e.g.
```
region-us
```
returns only multi-region
```
US
```
metadata and does not include single regions like
```
region-us-central1
```
).
No Multi-Region Aggregation in SQL: Region qualifiers cannot be joined cross-region in a single query (e.g.
```
region-us
```
cannot join
```
region-eu
```
).
Uncached Execution & Minimum Scan Size:
```
INFORMATION_SCHEMA
```
query results are never cached. On-demand queries incur a minimum of 10 MB of data processing charges per execution.

强制分区与时间过滤： 始终按
```
creation_time
```
（例如
```
creation_time >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 3 DAY)
```
）或
```
usage_date
```
进行过滤，避免全量元数据表扫描。
排除脚本包装器： 聚合计算开销时添加
```
AND (statement_type != 'SCRIPT' OR statement_type IS NULL)
```
，避免重复计算父脚本和子作业。
列裁剪： 切勿对
```
INFORMATION_SCHEMA
```
使用
```
SELECT *
```
；仅投影所需的列。
试运行与成本估算： 执行复杂查询、多视图连接或大范围扫描前，使用试运行（
```
bq query --dry_run --use_legacy_sql=false "{query}"
```
或API的
```
dryRun=true
```
参数）来验证语法并零成本估算
```
totalBytesProcessed
```
。
空区域范围（0行结果）： 如果执行位置与限定符匹配，但项目在该区域没有数据集或作业，查询会成功执行并返回0行。切勿假设0行意味着0使用量——务必验证目标数据集的位置。
非层级化区域范围： 区域限定符不具有层级关系。多区域不包含单区域（例如
```
region-us
```
仅返回多区域
```
US
```
的元数据，不包含
```
region-us-central1
```
等单区域）。
SQL中不支持跨区域聚合： 单个查询中不能跨区域连接不同的区域限定符（例如
```
region-us
```
不能连接
```
region-eu
```
）。
无缓存执行与最小扫描大小：
```
INFORMATION_SCHEMA
```
查询结果永远不会被缓存。按需查询每次执行至少产生10 MB的数据处理费用。

Domain References & SQL Queries

领域参考与SQL查询

Telemetry Query Guides

遥测查询指南

On-Demand Compute: Billed Bytes (
```
references/compute_ondemand_billable.md
```
): Authoritative Golden CTE (
```
bytes_billed_cte
```
), timezone-aligned billing date extraction (PST8PDT), BQML CREATE_MODEL 50x multiplier rules, script wrapper deduplication, and row-level security (RLS) masking checks.
Capacity Compute: Billable Slots & Commitments (
```
references/compute_capacity_billable.md
```
): Query templates for auditing billable capacity hours across 1-Year/3-Year commitments, uncovered baseline PAYG slots, and dynamic autoscaling hours.
Storage Footprints & Usage (Bytes Stored) (
```
references/storage_footprints.md
```
): Storage snapshot queries, compression ratio calculations, Time Travel / Fail-Safe churn, daily average GiB time-integrals, and billing model evaluation.

按需计算：计费字节数（
```
references/compute_ondemand_billable.md
```
）：权威的黄金CTE（
```
bytes_billed_cte
```
）、与时区对齐的计费日期提取（PST8PDT）、BQML CREATE_MODEL 50倍乘数规则、脚本包装器去重、行级安全（RLS）掩码检查。
容量计算：计费槽位与承诺（
```
references/compute_capacity_billable.md
```
）：用于审计跨1年/3年承诺、未覆盖的基准PAYG槽位和动态自动扩缩容小时数的计费容量小时数的查询模板。
存储占用与使用情况（存储字节数）（
```
references/storage_footprints.md
```
）：存储快照查询、压缩率计算、时间旅行/故障安全变动量、日均GiB时间积分、计费模型评估。

Performance & Troubleshooting Guides

性能与故障排查指南

Job Performance Queries (
```
references/job_performance_queries.md
```
): Queries for evaluating individual and aggregate job performance, stage bottleneck flags, comparable jobs via normalized literals (
```
query_info.query_hashes.normalized_literals
```
), BI Engine acceleration, metadata cache (cmeta) acceleration, and execution variance outliers.
Resource Contention Queries (
```
references/resource_contention_queries.md
```
): Queries for diagnosing slot contention, queue latency, per-minute concurrency/queue timelines, and 1-second reservation slot saturation.
Capacity & Configuration Queries (
```
references/capacity_and_configuration_queries.md
```
): Queries for evaluating second-by-second baseline/max capacity ceilings, autoscaling saturation timelines, and auditing configuration changes (
```
RESERVATION_CHANGES_BY_PROJECT
```
,
```
ASSIGNMENT_CHANGES_BY_PROJECT
```
).

作业性能查询（
```
references/job_performance_queries.md
```
）：用于评估单个和聚合作业性能、阶段瓶颈标记、通过归一化字面量（
```
query_info.query_hashes.normalized_literals
```
）查找可比作业、BI Engine加速、元数据缓存（cmeta）加速、执行方差异常值的查询。
资源争用查询（
```
references/resource_contention_queries.md
```
）：用于诊断槽位争用、队列延迟、每分钟并发/队列时间线、1秒级预留槽位饱和度的查询。
容量与配置查询（
```
references/capacity_and_configuration_queries.md
```
）：用于评估逐秒基准/最大容量上限、自动扩缩容饱和度时间线、审计配置变更（
```
RESERVATION_CHANGES_BY_PROJECT
```
、
```
ASSIGNMENT_CHANGES_BY_PROJECT
```
）的查询。

Schema Dictionaries (Column Definitions & Units)

模式字典（列定义与单位）

Compute & Capacity Schema Dictionary (

references/schema_compute.md

): Complete column dictionary, physical units, and least-privilege IAM roles for all compute, job, session, reservation, capacity commitment, and assignment views (

JOBS*

JOBS_TIMELINE*

SESSIONS_BY_USER

SESSIONS_BY_PROJECT

RESERVATIONS*

RESERVATION_CHANGES*

RESERVATIONS_TIMELINE*

CAPACITY_COMMITMENTS*

CAPACITY_COMMITMENT_CHANGES_BY_PROJECT

ASSIGNMENTS*

ASSIGNMENT_CHANGES_BY_PROJECT

Storage & Data Catalog Schema Dictionary (

references/schema_storage.md

): Complete column dictionary, physical units, and least-privilege IAM roles for all table storage, partition, column, snapshot, dataset, constraint, and replication views (

TABLE_STORAGE*

TABLE_STORAGE_USAGE_TIMELINE*

TABLES*

TABLE_OPTIONS

COLUMNS

COLUMN_FIELD_PATHS

PARTITIONS

VIEWS

MATERIALIZED_VIEWS

TABLE_SNAPSHOTS*

TABLE_CONSTRAINTS

KEY_COLUMN_USAGE

SCHEMATA*

SCHEMATA_OPTIONS

SCHEMATA_REPLICAS*

SCHEMATA_LINKS

SHARED_DATASET_USAGE

Platform, Governance & Ingestion Schema Dictionary (

references/schema_others.md

): Complete column dictionary, physical units, and least-privilege IAM roles for all remaining views including Access Control (

OBJECT_PRIVILEGES

ROW_ACCESS_POLICIES

ROW_ACCESS_POLICY_OPTIONS

), Streaming Ingestion (

STREAMING_TIMELINE_BY_PROJECT*

WRITE_API_TIMELINE_BY_PROJECT*

), Configuration Options (

PROJECT_OPTIONS*

EFFECTIVE_PROJECT_OPTIONS

ORGANIZATION_OPTIONS*

ORGANIZATION_OPTIONS_CHANGES

), Insights & Recommendations (

RECOMMENDATIONS*

INSIGHTS

), and Indexes/BI Engine/Routines (

SEARCH_INDEXES*

SEARCH_INDEX_COLUMNS

SEARCH_INDEX_OPTIONS

VECTOR_INDEXES*

VECTOR_INDEX_COLUMNS

VECTOR_INDEX_OPTIONS

BI_CAPACITIES

BI_CAPACITY_CHANGES

ROUTINES*

ROUTINE_OPTIONS

PARAMETERS

计算与容量模式字典（

references/schema_compute.md

）：所有计算、作业、会话、预留、容量承诺和分配视图（

JOBS*

、

JOBS_TIMELINE*

、

SESSIONS_BY_USER

、

SESSIONS_BY_PROJECT

、

RESERVATIONS*

、

RESERVATION_CHANGES*

、

RESERVATIONS_TIMELINE*

、

CAPACITY_COMMITMENTS*

、

CAPACITY_COMMITMENT_CHANGES_BY_PROJECT

、

ASSIGNMENTS*

、

ASSIGNMENT_CHANGES_BY_PROJECT

）的完整列字典、物理单位和最小权限IAM角色。

存储与数据目录模式字典（

references/schema_storage.md

）：所有表存储、分区、列、快照、数据集、约束和复制视图（

TABLE_STORAGE*

、

TABLE_STORAGE_USAGE_TIMELINE*

、

TABLES*

、

TABLE_OPTIONS

、

COLUMNS

、

COLUMN_FIELD_PATHS

、

PARTITIONS

、

VIEWS

、

MATERIALIZED_VIEWS

、

TABLE_SNAPSHOTS*

、

TABLE_CONSTRAINTS

、

KEY_COLUMN_USAGE

、

SCHEMATA*

、

SCHEMATA_OPTIONS

、

SCHEMATA_REPLICAS*

、

SCHEMATA_LINKS

、

SHARED_DATASET_USAGE

）的完整列字典、物理单位和最小权限IAM角色。

平台、治理与摄入模式字典（

references/schema_others.md

）：所有其余视图的完整列字典、物理单位和最小权限IAM角色，包括访问控制（

OBJECT_PRIVILEGES

、

ROW_ACCESS_POLICIES

、

ROW_ACCESS_POLICY_OPTIONS

）、流摄入（

STREAMING_TIMELINE_BY_PROJECT*

、

WRITE_API_TIMELINE_BY_PROJECT*

）、配置选项（

PROJECT_OPTIONS*

、

EFFECTIVE_PROJECT_OPTIONS

、

ORGANIZATION_OPTIONS*

、

ORGANIZATION_OPTIONS_CHANGES

）、洞察与建议（

RECOMMENDATIONS*

、

INSIGHTS

）、索引/BI Engine/例程（

SEARCH_INDEXES*

、

SEARCH_INDEX_COLUMNS

、

SEARCH_INDEX_OPTIONS

、

VECTOR_INDEXES*

、

VECTOR_INDEX_COLUMNS

、

VECTOR_INDEX_OPTIONS

、

BI_CAPACITIES

、

BI_CAPACITY_CHANGES

、

ROUTINES*

、

ROUTINE_OPTIONS

、

PARAMETERS

）。

bigquery-observability

Original

Translation

BigQuery Observability

BigQuery 可观测性

Tool Selection

工具选择

Prerequisites & Environment Setup

前提条件与环境设置

Workflow

工作流

Best Practices for Writing
`INFORMATION_SCHEMA`
Queries

编写
`INFORMATION_SCHEMA`
查询的最佳实践

Qualification Syntax & Scope Matching

限定语法与范围匹配

Principle of Least Privilege & Scope Selection

最小权限原则与范围选择

Execution Guardrails & Query Invariants

执行防护与查询不变式

Domain References & SQL Queries

领域参考与SQL查询

Telemetry Query Guides

遥测查询指南

Performance & Troubleshooting Guides

性能与故障排查指南

Schema Dictionaries (Column Definitions & Units)

模式字典（列定义与单位）

bigquery-observability

Original

Translation

BigQuery Observability

BigQuery 可观测性

Tool Selection

工具选择

Prerequisites & Environment Setup

前提条件与环境设置

Workflow

工作流

Best Practices for Writing INFORMATION_SCHEMA Queries

编写INFORMATION_SCHEMA查询的最佳实践

Qualification Syntax & Scope Matching

限定语法与范围匹配

Principle of Least Privilege & Scope Selection

最小权限原则与范围选择

Execution Guardrails & Query Invariants

执行防护与查询不变式

Domain References & SQL Queries

领域参考与SQL查询

Telemetry Query Guides

遥测查询指南

Performance & Troubleshooting Guides

性能与故障排查指南

Schema Dictionaries (Column Definitions & Units)

模式字典（列定义与单位）

Best Practices for Writing
`INFORMATION_SCHEMA`
Queries

编写
`INFORMATION_SCHEMA`
查询的最佳实践