Generated banner for Google Cloud Slo Alert Configuration
Generated logo for Google Cloud Slo Alert Configuration

Google Cloud Slo Alert Configuration

GoogleOfficialPublished by Google

  • Skill
  • Workflow
  • Cloud and DevOps
  • Apache-2.0
  • No issues found

From the author

Configures Cloud Monitoring PromQL-based Service Level Objective (SLO) alerting policies on Google Cloud for resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.
— the description by Google

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill acts as a structured setup wizard to help users define and configure Service Level Objective (SLO) alerting policies within Google Cloud. It guides the user through a four-step process: defining the service scope, setting service level targets, identifying the Service Level Indicator (SLI), and establishing alerting strategies. The skill automates the generation of Terraform code, specifically utilizing the google_monitoring_alert_policy resource and PromQL-based conditions, while ensuring best practices for SRE-focused reliability monitoring are applied.

What it does

  • Guides users through a 4-step workflow to define SLO parameters.
  • Generates Terraform (.tf) files for Cloud Monitoring alerting policies.
  • Uses PromQL for defining alert conditions.
  • Automatically includes required user labels for policy tracking.
  • Provides SRE best practice suggestions for SLO targets and burn rates.
  • Integrates with App Hub for resource scoping.

When to use it

  • When you need to create a new SLO alerting policy in Google Cloud.
  • When you want to standardize SLO configurations using Terraform.
  • When you need assistance determining appropriate SLI metrics or burn rate strategies.
  • When monitoring resources registered in Google Cloud App Hub.

Advantages

  • Ensures consistent SLO configuration through a structured wizard.
  • Reduces manual effort by generating ready-to-use Terraform code.
  • Promotes SRE best practices by suggesting standard reliability targets.
  • Simplifies complex PromQL alert logic for SLOs.
  • Maintains auditability by tagging generated policies with specific user labels.

Usage examples

“I need to set up an SLO alert for my backend service.”
The agent will initiate the 4-step wizard, asking for the service scope, target reliability, SLI metrics, and burn rate preferences to generate the Terraform configuration.
“Help me configure an SLO with SRE best practices.”
The agent will skip manual data gathering and apply recommended defaults, such as a 99.9% target over 28 days, and generate the corresponding Terraform code.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/google/google-cloud-slo-alert-configuration/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip google-cloud-slo-alert-configuration.zip -d .agents/skills

Documentation by Google

SLO Alert Configuration Setup Wizard

This skill guides the user through a structured conversation to configure Cloud Monitoring PromQL-based Service Level Objective (SLO) alerting policies on Google Cloud in Terraform. Your role is to act as a setup wizard that conceptually models the 4 key components of an SLO API (Service Scope, Service Level, SLI, and Alert Condition), gathers the requirements, and outputs a Terraform configuration.

Attribution

MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:google-cloud-slo-alert-configuration)" and append agent-skills/1.0 (skill:google-cloud-slo-alert-configuration) to User-Agent headers.

CRITICAL RULES

  • Structured Conversation: You MUST follow the 4-step wizard workflow below.

  • Gather Missing Information: Evaluate all 4 steps below first. Ask the user for all missing information across all steps in a single response.

    • DO NOT stop after finding the first missing piece of information.

    • DO NOT use the ask_question tool. You must ask questions using plain text in your response and end your turn to wait for the user to reply.

    • DO NOT write the Terraform configuration if information is missing.

  • Skip What Is Known: If the user has already provided information for a step in their previous messages or initial prompt DO NOT ask them for it. Move to the next missing piece of information. If ALL information for Steps 1-4 is provided, call write_to_file to generate the Terraform configuration without asking for permission to proceed.

  • Provide Best Practices: Whenever you ask the user a question, you MUST explicitly state the recommended "Best Practice".

  • Best Practice Shortcut: If the user asks for "best practices" or similar, do not overwrite their explicit inputs. SKIP all remaining data gathering and keep any specific targets or custom metrics they provided. For all fields left blank, apply the recommended defaults defined in the "SRE Best Practice Suggestion" of each step.

  • User Labels: Include a user_labels block in all google_monitoring_alert_policy resources to track policies created by this skill:

    user_labels = {
      created-with-google-skill = "google-cloud-slo-alert-configuration"
    }
  • Terraform Output: Write the generated observability configuration ONLY as Terraform (.tf) files using the google_monitoring_alert_policy resource and condition_prometheus_query_language resources.

  • Alert Strategy: ALWAYS include an alert_strategy block with an auto_close setting. Leave notification_channels empty unless the user provides one. Provide plain-English explanations of the PromQL math before finalizing the conversation.


SETUP WIZARD WORKFLOW

Step 1: Define ServiceScope
  1. Check Context: Identify target resource, service, workload, or application the user wants to monitor. If you already know, proceed. Otherwise ask the user to identify it.

  2. Autonomous Investigation: If the user specified a project or general service name without providing specifics, autonomously use gcloud to discover the target services in their environment. If multiple services or workloads are discovered, list all of them and suggest applying SLO ONLY to the most critical backend services as a best practice.

    If you struggle to identify potential resources, ask the user to specify.

  3. Identify Underlying Infrastructure: To resolve the correct PromQL metric, you MUST know the underlying Google Cloud resource type.

    • If the user only provides a logical name or an App Hub Service/Workload name such as projects/.../services/frontend or projects/.../workloads/backend, you still need to know the underlying infrastructure.

    • If the prompt provides the underlying infrastructure, use that information. Do NOT attempt to discover it.

    • If you don't know the underlying infrastructure but have a resource identified, you MUST proactively use gcloud to discover the infrastructure. If you struggle to identify the resource type, ask the user to specify.

  4. Label Scoping:

    • If the user explicitly mentions the resource is in App Hub or provides an App Hub URI like projects/.../locations/.../applications/..., use App Hub labels and consult references/app_hub_labels.md to identify the correct group-by fields.

    • Otherwise, assume it is a standard Google Cloud resource and use standard grouping labels such as project_id, location, service_name for Cloud Run.

    Example gcloud commands:

    • gcloud --quiet apphub applications services list --application=- --location=-

    • gcloud --quiet apphub applications workloads list --application=- --location=-

    • gcloud --quiet asset search-all-resources

    • gcloud --quiet run services list

    • gcloud --quiet apphub applications services describe <service> --application=<app> --location=<loc>

    • gcloud --quiet apphub applications workloads describe <workload> --application=<app> --location=<loc>

    • gcloud --quiet asset search-all-resources --query=<name>

    Graceful Fallback: If a command exits with an error such as API not enabled or permission denied, DO NOT try to troubleshoot it and DO NOT use the schedule tool to wait. Immediately fall back to asking the user to provide the missing information.

Step 2: Define ServiceLevel Target
  1. Check Context: If the user has already provided a Service Level Target percentage, an SLI condition/threshold, and a measurement period proceed to the next step. Otherwise, if any are missing, you MUST ask for them.

    • Service level target percentages include P-values such as PXX, decimals such as 0.XX, and percentages like XX%.

    • Example SLI conditions and thresholds include latency < 500ms or non-5XX responses.

  • Prompt: Ask the user for their target reliability, condition/threshold (if applicable), measurement period, and evaluation intervals ONLY if they are missing.

  • SRE Best Practice Suggestion: "SRE Best Practice recommends starting with a 99.9% (3 nines) slo_target measured over a rolling 28-day rolling_period, as this aligns well with typical release cycles and provides a reasonable error budget."

Step 3: Define ServiceLevelIndicator / SLI
  1. Check Context: Has the user specified the exact metric name such as run.googleapis.com/request_count? If yes, proceed to the next step. Otherwise, if the user only says "availability" or "latency" without specifying the EXACT metric name, you may infer the name from the service type provided a metric for that type is defined in the references. If the user provides a custom metric and a threshold, assume it is a Distribution metric and do not ask for further metric details.

    • You MUST output valid metrics defined in references/service_metrics.md. If the exact resource type and metric is not listed, check the public documentation in references/service_metrics.md to find the exact metric. If you still cannot find it, you MUST stop and ask the user to provide the custom metric.

  2. Prompt: Ask the user what specific metric they want to use. You MUST suggest the inferred standard metric as the recommended best practice. When interpreting incomplete requests, you MUST explicitly propose the specific metric string and describe the ratio-based or window-based definition to the user for confirmation before proceeding.

  3. Metric Mapping: Consult references/service_metrics.md to find the exact PromQL metric string for the Resource Type identified in Step 1 section 3. If the requested metric type does not exist for the resource in the references or the primary public documentation, you MUST explicitly inform the user that there is no default metric and ask them to provide the specific custom metric name. You MUST provide guidance on how a custom latency metric might be structured.

    • CRITICAL: If the primary documentation does not list a default metric, you MUST NOT try to piece together advanced metrics. Ask the user to provide the custom metric.

  4. Evaluation Method: Default the EvaluationType to REQUEST_BASED unless the user specifically describes a window-based requirement, typically denoted by "good minutes" or "bad minutes".

    • Window-Based Lookback Period: If the user indicates a window-based evaluation, you need to know the duration of the lookback windows and the evaluation interval for each window. You MUST ask the user to specify both the lookback duration and the evaluation interval if they have not already provided them. You CANNOT generate an alerting policy without this configuration.

  5. SRE Best Practice Suggestion: SRE Best Practice recommends starting with two SLIs:

    • Availability: a Ratio SLI comparing successful requests typically defined as non-5XX responses, to total requests evaluated as REQUEST_BASED.

    • Latency: a Distribution SLI evaluated as WINDOW_BASED such as 99% of 5-minute windows must meet a 300ms threshold.

Step 4: Define Alerting Policy
  1. Check Context: Has the user specified burn rates? If yes, proceed to the next step. Otherwise, ask the user to specify a burn rate strategy and provide a best practice suggestion.

  2. SRE Best Practice Suggestion: SRE Best Practice recommends both a multi-window fast burn and multi-window slow burn.

    • Multi-Window Fast Burn: Factor 14.4 over 1h and 5m windows, catching severe outages quickly without false positives.

    • Multi-Window Slow Burn: Factor 1 over 3d and 6h windows, catching system degradation.

Step 5: Generate Configuration
  1. Look up the corresponding PromQL template from references/promql_templates.md based on the user's choices. Use a Window-Based template for window-based SLOs.

  2. Populate the template with the ServiceScope labels, ServiceLevel targets, and ServiceLevelIndicator metrics.

  3. Wrap it in Terraform (google_monitoring_alert_policy), ensuring the user_labels block includes created-with-google-skill = "google-cloud-slo-alert-configuration".

  4. Present the .tf block with a plain English explanation of the math.

  5. In the final summary, inform the user that the alert policies have been tagged with the created-with-google-skill = "google-cloud-slo-alert-configuration" user label to track policies created by this skill.

  6. CRITICAL: Explicitly warn the user in the final summary if no notification channels are configured. Inform them that you can assist with setting those up if they would like.


Reporting Issues

Report bugs or improvements for this skill at Google Skills Issues.

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Google
Publisher
Google (Official)
Source
google/skills · skills/cloud/google-cloud-slo-alert-configuration · commit 2194d3b
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download google-cloud-slo-alert-configuration.zip