google-cloud-slo-alert-configuration

Generates Terraform SLO alerting policies with PromQL burn-rate queries for Google Cloud services.

19.1k|1.5k|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/google/skills --skill google-cloud-slo-alert-configuration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-cloud-slo-alert-configuration
Source: https://github.com/google/skills/tree/main/skills/cloud/google-cloud-slo-alert-configuration
Command: npx skills add https://github.com/google/skills --skill google-cloud-slo-alert-configuration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing correct PromQL-based Service Level Objective (SLO) alerting policies for Google Cloud requires deep knowledge of SRE burn-rate math, metric naming conventions, and Terraform syntax. This Skill guides you through a structured wizard to produce a valid Terraform configuration without manual PromQL authoring.

Core Features & Use Cases

  • Guided 4-Step Wizard: Walks through Service Scope, Service Level target, SLI metric selection, and burn-rate alerting strategy, asking only for missing information.
  • PromQL Template Library: Provides single-window, multi-window, and window-based burn-rate templates, plus prebuilt queries for Cloud Run, Vertex AI Reasoning Engine, and App Hub services.
  • Terraform Output: Generates google_monitoring_alert_policy resources with condition_prometheus_query_language, auto-close alert strategy, and tracking user labels.
  • Use Case: You want a 99.9% availability SLO on a Cloud Run service with fast-burn and slow-burn alerts. The Skill discovers the service via gcloud, maps the correct run.googleapis.com/request_count metric, and outputs a ready-to-apply .tf file.

Quick Start

Ask the assistant to configure an SLO alerting policy for your Cloud Run service with a 99.9% availability target over a 28-day rolling window.

Frequently Asked Questions about google-cloud-slo-alert-configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an SLO alerting policy for Google Cloud in Terraform?

Use this Skill's guided wizard to define the service scope, SLO target, SLI metric, and burn-rate strategy. It generates a google_monitoring_alert_policy resource with a condition_prometheus_query_language block containing the PromQL burn-rate query.

How do I write a PromQL burn rate alert for an SLO?

Burn-rate alerts compare the error ratio against (1 - SLO target) multiplied by a burn factor. The Skill provides templates for fast burn (factor 14.4 over 1h and 5m windows) and slow burn (factor 1 over 3d and 6h windows) following Google SRE workbook guidance.

Which metrics does the SLO skill support for Cloud Run and GKE?

Cloud Run uses run.googleapis.com/request_count for availability and request_latencies for latency. GKE workloads registered in App Hub use service/server/request_count and service/server/response_latencies; non-registered workloads require custom metric names.

Can I configure SLO alerts for App Hub services and workloads?

Yes. When a resource is registered in App Hub, the Skill scopes PromQL queries using metadata_system_apphub labels for application, service, or workload. It consults reference documentation to verify which labels apply to each metric type.

When should I not use this SLO configuration skill?

Do not use it for standard (non-SLO) alerting policies such as simple threshold alerts on CPU or disk usage. It is designed specifically for PromQL-based SLO burn-rate alerting and always generates Terraform output.