skilld
All skills
google avatar

/cloud-logging-query-generation

@becc4b8
by googlegoogle/skills21k stars
1,698

Generates Logging Query Language (LQL) queries for Google Cloud Logging from natural language. Use this skill when you need to query log data or when you are debugging issues. You can filter log data by Google Cloud service. Don't use this skill to query other databases, such as SQL or Cloud Spanner.

Ask your Agent

Use this Skill: https://skilld.dev/gh/google/skills/cloud-logging-query-generation

This session only. Nothing lands on disk.

referencesquery_cloud_run.md

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

Cloud Run LQL queries

Base schema and structural patterns

Cloud Run workloads are split into two primary paradigms: Services (which respond to HTTP requests) and Jobs (which execute to completion). Determine which resource is being targeted before querying.

Core resource types

  • Cloud Run Services (cloud_run_revision): Use this when querying logs for an HTTP-driven service deployed to Cloud Run.
  • Cloud Run Jobs (cloud_run_job): Use this when querying logs for a batch or parallel execution pipeline deployed to Cloud Run.

Log types (service invocations and stdout)

Cloud Run splits infrastructure routing telemetry away from the application's actual standard streams:

  • Ingress Telemetry: Use log_id("run.googleapis.com/requests") to capture the HTTP metadata (status codes, latency, caller IP, URL) generated by the Cloud Run gateway receiving the request.
  • Application Payload: Use log_id("run.googleapis.com/stdout") or log_id("run.googleapis.com/stderr") to capture logs explicitly printed by the container.

Execution correlation and concurrency

Cloud Run handles concurrent requests out of the box. Therefore, attempting to correlate logs via a simple execution ID label is usually an anti-pattern.

  • Trace ID: To trace all stdout/stderr payloads belonging to a single specific HTTP request log, apply a filter matching the trace string. (For example: trace="projects/<PROJECT_ID>/traces/<TRACE_ID>").

Example queries

Cloud Run logs for a specific job

Variables to replace: <JOB_NAME>

resource.type="cloud_run_job" AND
resource.labels.job_name="<JOB_NAME>"

Cloud Run logs for a specific revision and service

Variables to replace: <SERVICE_NAME>

resource.type="cloud_run_revision" AND
resource.labels.service_name="<SERVICE_NAME>"

Source: SKILL.md on GitHub

Third-party checks

No alerts9d3 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    This skill is designed to generate Logging Query Language (LQL) queries for Google Cloud Logging from natural language input. It provides comprehensive reference guides, syntax rules, and examples for various Google Cloud services. No security issues were detected.

  • Socket9d

    No alerts

  • Snyk9d

    Risk: LOW · No issues

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/cloud-logging-query-generation