Skip to main content
skill CX Codex official · Google

cloud-monitoring-alert-configuration — Claude Code skill

The cloud-monitoring-alert-configuration Claude Code skill configures Cloud Monitoring alert policies with Terraform and PromQL. It activates for creating, reviewing, migrating, or deduplicating those policies.

Apache-2.0 ★ 24,522 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add google/skills --skill cloud-monitoring-alert-configuration -a claude-code
Open on GitHub

What cloud-monitoring-alert-configuration does

The skill creates and reviews Cloud Monitoring alert policies for Cloud Run, GKE, Compute Engine, AI Hypercomputer, Vertex AI Agent Engine, and other Google Cloud resources. It uses Terraform and PromQL; log-based alerts cover lifecycle and audit events.

Its rules address latency, traffic, errors, and resource saturation. Requests for SLOs, error budgets, or burn-rate alerts go to google-cloud-slo-alert-configuration. Standalone PromQL authoring, log searches, and billing audits fall outside its scope.

The skill waits for explicit confirmation before changing infrastructure, enabling telemetry, or applying Terraform. When notification channels are missing from the request, it explains that the policies will have no attached channels and asks whether to configure them before deployment.

What it helps with

  • create Cloud Monitoring alerts for Cloud Run or GKE
  • review and migrate Terraform alert policies
  • remove duplicate alert policies
  • set up latency, traffic, and error signals

Example prompts for the agent

  • Create Cloud Monitoring policies for Cloud Run latency and errors.
  • Review the GKE Terraform alert policies and find duplicates.
  • Move the Compute Engine alerts to PromQL.

How to install cloud-monitoring-alert-configuration

1Skills CLI (Vercel)

npx skills add google/skills --skill cloud-monitoring-alert-configuration -a claude-code

2Manually: put the files in place

~/.claude/skills/cloud-monitoring-alert-configuration/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cloud-monitoring-alert-configuration/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about cloud-monitoring-alert-configuration

How do I install cloud-monitoring-alert-configuration in Claude Code?

Run npx skills add google/skills --skill cloud-monitoring-alert-configuration -a claude-code. The skill file is at ~/.claude/skills/cloud-monitoring-alert-configuration/SKILL.md.

What does cloud-monitoring-alert-configuration do?

It creates, reviews, migrates, and deduplicates Cloud Monitoring policies defined with Terraform and PromQL. It hands SLO requests to a separate skill.

What requests are outside the skill's scope?

It does not handle standalone PromQL query writing without alert setup, log searches, or cloud billing audits.

Source text

SKILL.md · Apache-2.0
---
name: cloud-monitoring-alert-configuration
metadata:
  version: "1.0.4"
  category: CloudObservabilityAndMonitoring
  support_tier: team
  tags: "cloud-monitoring, alerting, terraform, promql, observability"
  comment: >-
    Consolidated from Cloud Monitoring alerting policy best practices across
    Cloud Run, Google Kubernetes Engine, Compute Engine, and Vertex AI Agent
    Engine.
  canonical_source: https://docs.cloud.google.com/monitoring/alerts.md.txt
description: >-
  Configures Cloud Monitoring alerting policies using Terraform and
  PromQL across Cloud Run, Google Kubernetes Engine (GKE), Compute Engine, AI
  Hypercomputer reservations, Vertex AI Agent Engine, and generic Google Cloud
  resources. Use when creating, reviewing, migrating, or deduplicating Terraform
  alerting policies for latency, traffic, error rates, saturation, host or
  reservation maintenance, GPU XID insights, or AI agent telemetry. Don't use
  for standalone PromQL query authoring without alerting, log querying, or
  billing cost audits.
---

# Configure Cloud Monitoring Alerts

Configure high-signal alerting policies in Cloud Monitoring using
Terraform (`google_monitoring_alert_policy`) and PromQL
(`condition_prometheus_query_language`).

## Usage Attribution

For all `gcloud` CLI, REST API, and MCP attribution requirements when executing
commands with this skill, follow the instructions in
[Usage Attribution](references/attribution.md).

## Enforce Core Alerting Rules

1.  **Apply the Four Golden Signals**: Cover latency, traffic, errors, and
    saturation for the target workload.
2.  **Use Dynamic Grouping**: Aggregate metrics by resource labels and
    parameterize thresholds with Terraform variables. Never hardcode ephemeral
    pod or instance identifiers.
3.  **Default to PromQL**: Use Prometheus Query Language (PromQL) for metric
    conditions, and use log-based alerts
    (`condition_matched_log` or `google_logging_metric`) for lifecycle and
    audit events.
4.  **Attach Skill Attribution Labels**: Always include `user_labels` with
    `created-with-google-skill = "cloud-monitoring-alert-configuration"` on
    every generated `google_monitoring_alert_policy` resource.
5.  **Require User Confirmation Before Mutating Resources**: Never execute
    commands that modify infrastructure, enable telemetry, create online
    monitors, or apply Terraform without waiting for explicit user confirmation.
6.  **Prompt for Notification Channels**: Alerting policies without notification
    channels incur charges without notifying anyone during an incident. Whenever
    notification channels are not specified in the user prompt across any
    workflow, explicitly inform the user that no notification channels are
    attached to the alerting policies, advise them to configure and attach
    notification channels before deploying, and ask at the end of your response
    if they want to configure notification channels.

## Route by Target Resource Type

Identify the target resource type and read only the matching reference file
directly. Never run directory listings or workspace file searches to look for
queries or `.tf` files unless the prompt
explicitly provides a file path. If a user asks to fix or validate a PromQL
query without providing the query text or a file path, construct a
representative broken-and-corrected query example directly.

### Configure Cloud Run Alerts

*   **HTTP Services**:
    [cloud_run_services.md](references/cloud_run_services.md)
*   **Batch Jobs**:
    [cloud_run_jobs.md](references/cloud_run_jobs.md)
*   **Worker Pools**:
    [cloud_run_worker_pools.md](references/cloud_run_worker_pools.md)

### Configure Google Kubernetes Engine Alerts

*   **PromQL Queries and Golden Signals**:
    [GKE PromQL Queries](references/kubernetes_promql_queries.md)
*   **Metrics Catalog and Open-Source Alerts**:
    [GKE Metrics](references/kubernetes_metrics_and_alerts_catalog.md)
*   **Prerequisites and Setup**:
    [GKE Setup](references/kubernetes_gke_configuration_prerequisites.md)

### Configure AI Agent Alerts

*   **Reliability**:
    [Reliability](references/agent_platform_reliability_alert_policies.md)
*   **Quality**:
    [Quality](references/agent_platform_quality_alert_policies.md)
*   **Cost**:
    [Cost](references/agent_platform_cost_alert_policies.md)
*   **Safety**:
    [Safety](references/agent_platform_safety_alert_policies.md)
*   **Security**:
    [Security](references/agent_platform_security_alert_policies.md)
*   **Telemetry Enablement**:
    [Telemetry](references/agent_platform_telemetry_enablement.md)
*   **Traffic Profiles**:
    [Historical](references/agent_platform_has_historical_traffic_data.md)
    and
    [No History](references/agent_platform_no_historical_traffic_data.md)

### Configure Compute Engine and AI Hypercomputer Alerts

*   **Compute Engine VMs, MIGs, GPU XID Insights, Host or Reservation
    Maintenance (`type=scheduled`, `unscheduled`, or `multiple`), and Machine
    or Domain Health**:
    [compute_engine_alerts.md](references/compute_engine_alerts.md)

### Configure Generic Resource Alerts

*   **Generic Workloads, Custom Metrics, MQL Migration, and HCL Deduplication**:
    [generic_alert_policies.md](references/generic_alert_policies.md)

### Delegate Service Level Objective Alerts

**Delegate to the `google-cloud-slo-alert-configuration` skill.** That skill
owns the SLO setup wizard, the burn-rate PromQL templates
(`references/promql_templates.md`), the SLI metric mapping
(`references/service_metrics.md`), and the App Hub scoping labels
(`references/app_hub_labels.md`). Do **NOT** duplicate those templates here or
claim that this skill owns its own SLO PromQL template library.

Delegate whenever the user asks for an **availability or latency SLO**, an
**error budget or burn-rate alert**, or a **Service Level Objective** on any
resource. When SLOs are only one part of a broader request (for example, a full
production alerting suite for a Cloud Run service), delegate the SLO policies
and continue generating the remaining golden-signal policies from the
resource-specific reference in the same response.

Every resource reference carries a **Context to hand off** list naming the SLI
metric, its good or bad filter, and the grouping labels — under a `## Delegate
Service Level Objective Alerts` heading for Cloud Run and generic resources, and
inside the SLO section itself for GKE and Agent Platform. Read it and pass that
context on, so the SLO skill does not repeat discovery you have already done.
When delegating, you MUST also:

1.  State the SLO target and window explicitly if the user gave them, or let the
    SLO skill apply its SRE defaults (99.9% over a rolling 28 days) if they did
    not.
2.  Require the returned policies to carry `user_labels` with
    `created-with-google-skill = "cloud-monitoring-alert-configuration"` so
    attribution stays consistent with the rest of the generated suite. This
    literal value does **NOT** change when you delegate: the label records the
    entry-point skill, not whichever skill supplied the template. Do **NOT**
    set `created-with-google-skill = "google-cloud-slo-alert-configuration"` on
    policies generated through this delegation.
3.  Preserve the burn-rate duration contract, which
    `google-cloud-slo-alert-configuration` does not specify: Fast Burn (`1h` and
    `5m` windows, factor `14.4`) carries `duration = "300s"`, and Slow Burn
    (`[3d]` and `[6h]` lookback, factor `1.0`) **omits the `duration` field
    entirely** — do not emit `duration = "0s"` in its place. Cloud Monitoring
    rejects a non-zero retest buffer when the lookback window exceeds 25 hours.
4.  When no notification channels are provided, inform the user that no
    notification channels are attached to the alerting policies, advise them to
    configure and attach notification channels, and ask if they want to
    configure notification channels.

> [!IMPORTANT]
> **Always tell the user about the referral, even on the fallback path.** Some
> reference files in this skill include standalone burn-rate templates to use
> when the `google-cloud-slo-alert-configuration` skill is not installed. If you
> emit policies from those fallback templates, your response MUST still tell the
> user that `google-cloud-slo-alert-configuration` owns SLO configuration, state
> that the emitted policies use the local fallback templates, and list the
> handoff context. Never silently present SLO policies as if this
> skill owned them.

> [!NOTE]
> **Exception**: Agent Platform (OpenTelemetry-instrumented AI agents on any
> runtime, including Vertex AI Agent Engine and Cloud Run) is the one resource
> whose Fast and Slow burn policies live in this skill and remain authoritative.
> Delegate only for SLO customization — see
> [Reliability](references/agent_platform_reliability_alert_policies.md).

## Delegate Related Observability Tasks

*   **Notification Channels**: Delegate to
    `cloud-monitoring-notification-channels-configuration` to configure email,
    PagerDuty, Pub/Sub, or Slack channels. When an alerting policy has no
    notification channels attached, inform the user that no notification
    channels are attached and that they should configure notification channels
    and attach them to the alerting policy.
*   **PromQL Authoring**: Delegate to `cloud-monitoring-promql-query` for
    standalone PromQL query authoring or metric exploration.

## Follow the Alert Configuration Workflow

1.  **Discover**: Identify target resources, metric schemas, and scoping
    projects using the lookup commands in the matching reference file (such as
    [discover_metric_schema.py](scripts/discover_metric_schema.py) for Compute
    Engine metrics and other Google Cloud resource metrics, or
    [gather_agent_info.py](scripts/agent_platform/gather_agent_info.py),
    [check_telemetry.py](scripts/agent_platform/check_telemetry.py),
    [analyze_traffic.py](scripts/agent_platform/analyze_traffic.py),
    [create_online_monitor.py](scripts/agent_platform/create_online_monitor.py),
    [list_trace_scope_table_names.py](scripts/agent_platform/list_trace_scope_table_names.py),
    and
    [list_log_scope_table_names.py](scripts/agent_platform/list_log_scope_table_names.py)
    for AI agents).
2.  **Route**: Load the reference file for the target resource type or delegate
    SLOs to `google-cloud-slo-alert-configuration`.
3.  **Generate**: Produce parameterized Terraform HCL configurations with
    required `user_labels`.
4.  **Validate**: When the loaded reference file requires a validation script
    (such as [lint_promql.py](scripts/lint_promql.py),
    [validate_config.py](scripts/kubernetes/validate_config.py),
    [lint_syntax.py](scripts/agent_platform/lint_syntax.py), or
    [scan_duplicates.py](scripts/agent_platform/scan_duplicates.py)), run or
    print that exact script command. Do not list or search the `scripts/`
    directory.
5.  **Explain and Prompt**: Explain each alert policy in plain English. When no
    notification channels are provided, tell the user that no notification
    channels are attached to the alerting policy, advise them to configure and
    attach notification channels, and ask if they want to configure notification
    channels.

© google · Apache-2.0 · google/skills

Similar skills

All skills for Cloud: AWS, Azure, GCP →

From the same set203

The whole set →
compute-spot-capacity-advice The compute-spot-capacity-advice Claude Code skill assesses Google Compute Engine Spot VM capacity and placement. It runs during batch planning, when comparing machine families or regions. CX Codex +1 ★ 24,522repo stars cloud-operator Delegates Google Cloud infrastructure operations to Cloud Operator via the autocloud MCP server. Triggers before modifying local Terraform or Kubernetes configs. CX Codex +1 ★ 24,522repo stars cloud-operator-share-context The cloud-operator-share-context Claude Code skill transfers existing Google Cloud operating notes to an operator agent’s memory. It runs when someone asks to import or save GCP context. CX Codex +1 ★ 24,522repo stars cloud-operator-setup The cloud-operator-setup Claude Code skill sets up an operator agent in a Google Cloud project. Run it to create your operator or start its setup. CX Codex +1 ★ 24,522repo stars cloud-armor-crs-rule-upgrader The cloud-armor-crs-rule-upgrader Claude Code skill upgrades Google Cloud Armor WAF rules from OWASP CRS 3.0 or 3.3 to CRS 4.22. It runs for policy audits and rule-set migrations. CX Codex +1 ★ 24,522repo stars bigquery-migration-validator The bigquery-migration-validator Claude Code skill checks whether BigQuery tables match their source. It runs during validation setup, execution, and investigation of migration mismatches. CX Codex +1 ★ 24,522repo stars bigquery-migration-metadata-extractor bigquery-migration-metadata-extractor — a skill for Claude Code runs catalog metadata and query log dumps from external warehouses into Cloud Storage. It triggers extraction jobs and parses summary statistics. CX Codex +1 ★ 24,522repo stars bigquery-migration-data-loader The bigquery-migration-data-loader Claude Code skill loads staged Parquet files into BigQuery and deploys translated views. It runs during target dataset setup and warehouse data migration. CX Codex +1 ★ 24,522repo stars

Project sponsors

Companies that keep this analytics open