Terminal
Terminal/Skill
Writes Terraform alerting policies in PromQL for Cloud Run services, jobs and worker pools, covering errors, latency and saturation.
By Google
Works with
npx skills add google/skills --skill cloud-run-alert-configurationProduction-grade observability for Cloud Run using Terraform and PromQL (Cloud Monitoring). Grounded in SRE practices, this skill focuses strictly on actionable user impact and scaling bounds.
'video-encoder', 'nightly-reconciliation', 'web-frontend', 'catalog-service', 'api-gateway', 'order-processor'), SKIP all workspace .tf file scanning (find_by_name, code_search, list_dir) and gcloud CLI discovery commands entirely.gcloud, terraform, or file search tools when the target name is already provided in the prompt. Instead, parameterize the project ID (variable "scoping_project_id" { default = "my-gcp-project" }) and target resource name in Terraform variables and proceed immediately to Step 2 (Configure Alerts).find_by_name or ls across root workspace directories..tf files in the immediate working directory for google_cloud_run_v2_service, google_cloud_run_service, or google_cloud_run_v2_job..tf files, attempt gcloud config get-value project and gcloud run services list. If any gcloud command fails (e.g., auth or metadata errors) or terraform is missing, immediately stop running CLI commands and output parameterized HCL using explicit variable defaults.project = var.scoping_project_id in all Terraform google_monitoring_alert_policy resources so the policy can target either a single project or a centralized Cloud Monitoring Metrics Scope.duration (Retest Window) Rules:
duration = "300s" (5m buffer) to absorb
transient blips and scale-up lag (except immediate job failure alerts
which use duration = "0s").duration
entirely (or set to 0s). Cloud Monitoring rejects PromQL queries
with duration set on lookbacks >25h (INVALID_ARGUMENT)..tf configurations using google_monitoring_alert_policy and condition_prometheus_query_language directly in your response.google_monitoring_alert_policy resource MUST include a user_labels block containing:
user_labels = {
created-with-google-skill = "cloud-run-alert-configuration"
}
alert_strategy { auto_close = "604800s" } and parameterize notification_channels = var.notification_channels..tf files or run gcloud to identify the target workload type and name. If gcloud auth fails, fall back immediately to default Terraform variables (var.scoping_project_id).duration = "0s").user_labels block (created-with-google-skill = "cloud-run-alert-configuration").