skilld
All skills
google avatar

/google-cloud-slo-alert-configuration

@becc4b8
by googlegoogle/skills21k stars
1,698

Configures PromQL-based Service Level Objective (SLO) alerting policies for Google Cloud 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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/google/skills/google-cloud-slo-alert-configuration

This session only. Nothing lands on disk.

referencesapp_hub_labels.md

≈533 tokens on demand. Your agent reads this file only when SKILL.md points to it.

App Hub Scope & Labels

CRITICAL NUANCE: Verify App Hub Labels! Not all Google Cloud metrics apply App Hub labels in the exact same way. Infrastructure Metrics: Usually attached as system metadata (metadata_system_apphub_... in PromQL). Instrumented Metrics: When included, attached as metric labels like apphub_application_id or might not have them attached by default.

REQUIRED ACTION: Because label support varies by resource type and metric, you must not guess. You must verify exactly which App Hub labels and PromQL mappings exist on that specific metric by reading the public documentation linked below before generating the final SLO configuration.

For full public documentation on label mappings across logs, metrics, and traces, refer to: https://docs.cloud.google.com/stackdriver/docs/observability/application-monitoring-labels.md.txt

When configuring an SLO that scopes to an App Hub Application, Service, or Workload and you have verified the labels exist, use the following standard metadata labels as your group by fields in PromQL queries:

App Hub Application Scope

If monitoring an entire App Hub Application, include these labels in your PromQL BY (...) clause:

  • metadata_system_apphub_host_project_id
  • metadata_system_apphub_location
  • metadata_system_apphub_application_id

App Hub Service Scope

If monitoring a specific App Hub Service, include these labels:

  • metadata_system_apphub_host_project_id
  • metadata_system_apphub_location
  • metadata_system_apphub_application_id
  • metadata_system_apphub_service_id

App Hub Workload Scope

If monitoring a specific App Hub Workload, include these labels:

  • metadata_system_apphub_host_project_id
  • metadata_system_apphub_location
  • metadata_system_apphub_application_id
  • metadata_system_apphub_workload_id

Example Usage:

sum(rate(run_googleapis_com:request_count[5m])) BY (metadata_system_apphub_host_project_id, metadata_system_apphub_location, metadata_system_apphub_application_id, metadata_system_apphub_service_id)

Source: SKILL.md on GitHub

Third-party checks

1 warning10d3 checks · Risk SAFE
  • Gen Agent Trust Hub10d

    This skill provides a structured wizard for configuring Service Level Objective (SLO) alerting policies on Google Cloud. It utilizes official Google Cloud CLI tools for resource discovery and retrieves current metric definitions from official documentation to generate Terraform configurations.

  • Socket10d

    No alerts

  • Snyk10d

    Risk: MEDIUM · 1 issue

Provenance

Signed by skilld at becc4b8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago

Capability

metadata
{
  "version": "1.0.0",
  "category": "CloudObservabilityAndMonitoring"
}

README badge

README badge for google/skills/google-cloud-slo-alert-configuration