Skip to content

Add gcp_job_monitoring skill for Data Cloud Admin and Workload Monitoring. - #467

Open
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_999612801
Open

copybara-service[bot] wants to merge 1 commit into
mainfrom
test_999612801

Conversation

@copybara-service

@copybara-service copybara-service Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Add gcp_job_monitoring skill for Data Cloud Admin and Workload Monitoring.

https://docs.google.com/document/d/1GzdDp1uaHisdxDJnfOViVvd9vzRoQ5VuQvQfe7m2eo0/edit?resourcekey=0-xEguGjH3LcF64huvf-07Zg&tab=t.0

Adds a platform-independent skill (gcp-job-monitoring) and zero-dependency Python helper CLI (scripts/gcp_job_monitor.py) that dynamically answers Data Cloud Admin & Practitioner job-monitoring queries across BigQuery and Dataproc Spark (Serverless Batches, Interactive Sessions, and Cluster Jobs):

  • Recent & active jobs (bq_list, spark_list) with --mine, --user, and --state filtering, plus automatic allUsers=true -> allUsers=false permission fallback when the caller lacks bigquery.jobs.listAll.
  • Most expensive BigQuery jobs (bq_top_cost) ranked by bytes billed (with estimated on-demand USD cost) and slot time.
  • Project-wide spend, slot & failure attribution (bq_summary) breaking down usage by user, by Edition / Slot Reservation (ON_DEMAND vs. ENTERPRISE), and top failure error reasons.
  • Hot tables analysis (bq_hot_tables) ranking referenced BigQuery tables by total bytes billed, slot time, query count, and distinct users.
  • Capacity & fleet monitoring (bq_reservations, spark_clusters) inspecting BigQuery slot reservations, autoscaling limits, capacity commitments, assignments, active Dataproc clusters, and Serverless interactive sessions.
  • Slowest jobs & single-job stage inspection (bq_slowest, spark_slowest, bq_describe, spark_describe) surfacing SQL text, per-stage queryPlan wait/compute/spill metrics, referenced tables, errors, and Serverless DCU-hours.
  • Supports --format=json, reusable CAA-safe RestClient for arbitrary GCP REST endpoints, and references/information_schema_queries.md for SQL/MCP environments.

…toring.

https://docs.google.com/document/d/1GzdDp1uaHisdxDJnfOViVvd9vzRoQ5VuQvQfe7m2eo0/edit?resourcekey=0-xEguGjH3LcF64huvf-07Zg&tab=t.0

Adds a platform-independent skill (`gcp-job-monitoring`) and zero-dependency Python helper CLI (`scripts/gcp_job_monitor.py`) that dynamically answers Data Cloud Admin & Practitioner job-monitoring queries across BigQuery and Dataproc Spark (Serverless Batches, Interactive Sessions, and Cluster Jobs):
- Recent & active jobs (`bq_list`, `spark_list`) with `--mine`, `--user`, and `--state` filtering, plus automatic `allUsers=true` -> `allUsers=false` permission fallback when the caller lacks `bigquery.jobs.listAll`.
- Most expensive BigQuery jobs (`bq_top_cost`) ranked by bytes billed (with estimated on-demand USD cost) and slot time.
- Project-wide spend, slot & failure attribution (`bq_summary`) breaking down usage by user, by Edition / Slot Reservation (`ON_DEMAND` vs. `ENTERPRISE`), and top failure error reasons.
- Hot tables analysis (`bq_hot_tables`) ranking referenced BigQuery tables by total bytes billed, slot time, query count, and distinct users.
- Capacity & fleet monitoring (`bq_reservations`, `spark_clusters`) inspecting BigQuery slot reservations, autoscaling limits, capacity commitments, assignments, active Dataproc clusters, and Serverless interactive sessions.
- Slowest jobs & single-job stage inspection (`bq_slowest`, `spark_slowest`, `bq_describe`, `spark_describe`) surfacing SQL text, per-stage `queryPlan` wait/compute/spill metrics, referenced tables, errors, and Serverless DCU-hours.
- Supports `--format=json`, reusable CAA-safe `RestClient` for arbitrary GCP REST endpoints, and `references/information_schema_queries.md` for SQL/MCP environments.

PiperOrigin-RevId: 999612801
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant