Agent skill · google

cloud-monitoring-alert-configuration

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.

What it needs

About 5k tokens when loaded.

What this skill does

Configure Cloud Monitoring Alerts Configure high-signal alerting policies in Cloud Monitoring using Terraform (googlemonitoringalertpolicy) and PromQL (conditionprometheusquerylanguage). Usage Attribution For all gcloud CLI, REST API, and MCP attribution requirements when executing commands with this skill, follow the instructions in Usage Attribution. 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 (conditionmatchedlog or googleloggingmetric) for lifecycle and audit events. 4. Attach Skill Attribution Labels: Always include userlabels with created-with-google-skill = "cloud-monitoring-alert-configuration" on every generated googlemonitoringalertpolicy 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. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/cloud-monitoring-alert-configuration

View the source on GitHub

Browse the @skills marketplace