AutoGineer
Generated banner for Cloud Logging Query Generation
Generated logo for Cloud Logging Query Generation

Cloud Logging Query Generation

GoogleOfficialPublished by Google

  • Skill
  • Tool integration
  • Cloud and DevOps
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Generates Logging Query Language (LQL) queries for Cloud Logging on Google Cloud 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.
— the description by Google

AutoGineer summary

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

This skill assists users in constructing precise Logging Query Language (LQL) queries for Google Cloud Logging. It provides structured guidance on syntax, resource types, and field filtering to help users debug issues or analyze log data. The skill adheres to specific formatting rules, including the use of double quotes for strings, capitalized boolean operators, and explicit grouping with parentheses. It also includes logic for handling audit logs and global keyword searches when specific schemas are unavailable.

What it does

  • Translates natural language requests into valid LQL queries.
  • Provides syntax enforcement for boolean operators and string literals.
  • Identifies correct resource types for various Google Cloud services.
  • Handles audit and admin log queries using specific protoPayload schemas.
  • Generates global search queries using the SEARCH function when schemas are unknown.
  • Applies mandatory attribution headers for direct CLI or API interactions.

When to use it

  • When you need to filter or search through Google Cloud logs.
  • When debugging specific service issues and requiring log data.
  • When you are unsure of the correct LQL syntax or resource type for a specific service.
  • When you need to extract audit logs for security or operational review.

Advantages

  • Reduces manual effort in writing complex LQL syntax.
  • Ensures adherence to Google Cloud logging best practices.
  • Provides service-specific guidance for accurate filtering.
  • Maintains consistent attribution for observability operations.

Usage examples

“Show me all error logs for my GCE instance named web-server-01.”
resource.type="gce_instance" AND resource.labels.instance_name="web-server-01" AND severity>=ERROR
“Find audit logs for BigQuery dataset deletions.”
resource.type="bigquery_dataset" AND protoPayload.methodName="google.cloud.bigquery.v2.DatasetService.DeleteDataset"

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/google/cloud-logging-query-generation/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip cloud-logging-query-generation.zip -d .agents/skills

Documentation by Google

Generate Logging Query Language queries

Use this skill to generate correct Logging Query Language (LQL) queries for Cloud Logging.

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:cloud-logging-query-generation)" and append agent-skills/1.0 (skill:cloud-logging-query-generation) to User-Agent headers.

Core rules

  1. Strict syntax requirements:

    • Always use double quotes (") for string literals. Do not use single quotes (').

    • Write boolean operators in all capitals: AND, OR, NOT.

    • Always use parentheses to group terms and explicitly enforce precedence.

  2. Common pitfalls:

    • Instance ID vs. Instance Name: For the gce_instance resource type, do NOT compare instance names to instance IDs. Instance names are strings (for example, my-instance). Instance IDs are numeric. If you only have the name, then search by instance name, SEARCH("my-instance"), or use resource.labels.instance_name if that label is available for the resource.

    • Resource Type Accuracy: Do not guess resource types. You must look up the correct resource.type value in the service-specific reference files. For example, use internal_http_lb_rule for Internal HTTP(S) Load Balancer rules when filtering by forwarding rule name or region (instead of http_load_balancer).

  3. Output format and placeholders:

    • Output only the raw LQL query text. Do not include conversational filler. Do not wrap the query in markdown code blocks unless explicitly requested by the user. Valid LQL comments (using --) are allowed, and are the ONLY acceptable way to include explanations or warnings.

    • Never block on missing variables. If the user's request lacks specific identifiers (like a project ID, instance name, or IP address), do not ask them for clarification. If the variable is required for a functional query (like a log bucket name for a regional log), insert an uppercase placeholder string wrapped in angle brackets (for example, "<PROJECT_ID>"). CRITICALLY: If you include a placeholder for a variable the user omitted, it will act as an explicit filter that causes logs to be missed. Therefore, you MUST omit the entire filter/line containing the placeholder if the field is not strictly required. For example, completely omit resource.labels.instance_id="..." if the user didn't specify an instance, but you MUST include logName=".../projects/<PROJECT_ID>/..." with a placeholder if constructing a regional log bucket query where a project ID is strictly required.

  4. Preferred fields:

    • Include resource.type and log_id restrictions when the query targets specific Google Cloud services or resources. Global queries (for example, "latest error logs") do not require these restrictions.

Detailed reference

Refer to references/api_reference.md for LQL syntax rules, including Operators, NULL handling, SEARCH, and Regex.

Service reference files

Before generating a query, you MUST read the examples for the specific service. LQL schemas and resource.type values are service-specific. Do not stop reading after finding the Base Schema in the file. You must verify if there are specific requirements for state tracking (like previousState) or resource-specific log IDs detailed in the paragraphs or specific query examples below the schema block.

For the following services, read the exact file listed:

For Google Cloud services that aren't listed: If the service is not listed above, write the LQL query based on your general knowledge.

Query generation rules

  1. Resource Types: Explicitly define the resource.type in your queries when focusing on specific services. For some queries, you may need to search across multiple types (for example, resource.type=("bigquery_project" OR "bigquery_dataset")).

  2. Audit and Admin Logs: If the user asks for audit logs, admin logs, API logs, or logs about who created, updated, deleted, read, or accessed a resource:

    • You MUST read references/query_audit_logs.md for the correct protoPayload schema paths and common examples.

    • If a specific example is not listed, guess the protoPayload.methodName by combining the service and verb. When guessing, you MUST use the scoped SEARCH() function (e.g., SEARCH(protoPayload.methodName, "compute.instances.insert")) instead of the exact match operator (=) to avoid version prefix mismatches. Do NOT use the colon operator (:) as it may cause substring false positives.

    • For generic API enable/disable events (e.g., a service was disabled), always use resource.type="audited_resource".

  3. Handling Unknown Schemas (Crucial): If the user asks to filter by a specific field or condition, and if you cannot find a matching example or schema in the reference files, then you must generate a query using global search.

    • Only specify jsonPayload.* or protoPayload.* field structures when you are certain of their exact name.

    • Use the SEARCH() function to find the keyword globally within the correct resource.type.

    • Mandatory LQL Comment: When delivering a query that uses SEARCH, you MUST add an LQL comment (using --) at the top of the query indicating you used a global keyword search because the exact schema wasn't in your references. Do NOT output conversational text, strictly adhere to the Output Format rule.

Supporting links

Files

references/query_compute_engine.md

Compute Engine (GCE) LQL queries

Table of contents

  • Base schema and structural patterns (L44-L101)

  • Core resource types (L50-L60)

  • Guest OS and application logs (Ops Agent) (L62-L72)

  • Boot and kernel logs (serial console) (L74-L81)

  • Google infrastructure system events (L83-L91)

  • User activity audit logs (L93-L101)

  • Example queries (L103-L467)

  • Activity audit logs for Compute Engine instances (L105-L112)

  • System logs (syslog) emitted by Compute Engine instances (L114-L121)

  • Compute Engine firewall rule deletion (L123-L131)

  • Compute Engine VM authlogs (L133-L140)

  • Compute Engine host error (L142-L155)

  • Compute Engine host memory alert (L157-L170)

  • Compute Engine host migrated (L172-L186)

  • Compute Engine VM terminated/preempted (L188-L197)

  • Compute Engine VM terminated due to scratch disk creation failure (L199-L213)

  • Compute Engine zone resource pool exhaustion (stockout) (L215-L226)

  • Compute Engine VM instance created (L228-L237)

  • Compute Engine VM instance deleted with name (L239-L248)

  • Compute Engine VM instance deleted with ID (L250-L259)

  • Compute Engine VM instance restarted (L261-L271)

  • Compute Engine Shielded VM boot integrity failure (L273-L282)

  • Compute Engine VM instance stopped by Guest OS (L284-L296)

  • Compute Engine Shielded VM boot file was blocked (L298-L307)

  • Persistent disk created (L309-L318)

  • Nodes added in sole-tenant node (L320-L331)

  • Autoscale events in sole-tenant node (L333-L343)

  • Manual snapshot taken (L345-L354)

  • Scheduled snapshot taken (L356-L366)

  • Snapshot schedule created (L368-L377)

  • Snapshot schedule attached (L379-L389)

  • Quota exceeded (L391-L400)

  • Query unhealthy instances in instance group (L402-L410)

  • Query instance group members within a time frame in UTC time format (L412-L423)

  • Instances added to instance group (L425-L434)

  • Instances removed from instance group (L436-L445)

  • Instance template set or updated (L447-L457)

  • Firewall logs (L459-L467)

Base schema and structural patterns

Compute Engine logs are highly segmented depending on whether you are analyzing the VM's internal operating system, Google's infrastructure events, or user-driven API audit logs.

Core resource types

  • VM Instances (gce_instance): The most common resource type. Use this when analyzing a running VM (Guest OS), its boot console, or its lifecycle events.

  • Storage (gce_disk, gce_snapshot): Use for operations on persistent disks and snapshots.

  • Networking (gce_firewall_rule, gce_route, gce_network): Use for infrastructure-level network changes, NOT for traffic flow logs.

  • Groups (gce_instance_group, gce_instance_template): Use for Managed Instance Group (MIG) scaling, creation, and health checks.

Guest OS and application logs (Ops Agent)

When a user asks to search for "errors inside my VM", "syslog", "auth requests", or "app logs":

  • Target resource.type="gce_instance".

  • These are usually ingested via the Ops Agent.

  • Filter by log_id("syslog"), log_id("winevt.raw"), or the custom file log_id.

  • The raw log string is found in textPayload (unstructured) or jsonPayload (structured).

Boot and kernel logs (serial console)

When a VM is unbootable, crashing on startup, or experiencing kernel panics:

  • Target resource.type="gce_instance".

  • Filter by log_id("serialconsole.googleapis.com/serial_port_1_output").

  • Search within textPayload (for example, "kernel panic", "Out of memory").

Google infrastructure system events

When a VM is preempted, terminated by Google, or migrated during a host error:

  • Target resource.type="gce_instance".

  • Filter by log_id("cloudaudit.googleapis.com/system_event").

  • System events are NOT driven by users, so they are logged as system events. Use protoPayload.methodName (for example, "compute.instances.hostError", "compute.instances.preempted").

User activity audit logs

When a user asks "who deleted my VM", "who stopped the instance", or "when was this disk attached":

  • Target the relevant resource type (gce_instance, gce_disk, etc.).

  • Filter by log_id("cloudaudit.googleapis.com/activity").

  • Use protoPayload.methodName (for example, "v1.compute.instances.delete", "v1.compute.disks.attach").

Example queries

Activity audit logs for Compute Engine instances

Variables to replace: None

resource.type="gce_instance" AND
log_id("cloudaudit.googleapis.com/activity")
System logs (syslog) emitted by Compute Engine instances

Variables to replace: None

resource.type="gce_instance" AND
log_id("syslog")
Compute Engine firewall rule deletion

Variables to replace: None

resource.type="gce_firewall_rule" AND
log_id("cloudaudit.googleapis.com/activity") AND
SEARCH(protoPayload.methodName, "firewalls.delete")
Compute Engine VM authlogs

Variables to replace: None

resource.type="gce_instance" AND
log_id("authlog")
Compute Engine host error

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
protoPayload.serviceName="compute.googleapis.com" AND
(SEARCH(protoPayload.methodName, "compute.instances.hostError")
OR
operation.producer:"compute.instances.hostError") AND
log_id("cloudaudit.googleapis.com/system_event") AND
resource.labels.instance_id="<INSTANCE_ID>" AND
severity=INFO
Compute Engine host memory alert

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
protoPayload.serviceName="compute.googleapis.com" AND
(jsonPayload.methodName:"compute.instances.host_event_notify"
OR
operation.producer:"compute.instances.host_event_notify") AND
log_id("cloudaudit.googleapis.com/host_event_notify") AND
resource.labels.instance_id="<INSTANCE_ID>" AND
severity=CRITICAL
Compute Engine host migrated

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
protoPayload.serviceName="compute.googleapis.com" AND
(SEARCH(protoPayload.methodName, "compute.instances.migrateOnHostMaintenance")
OR
operation.producer:
"compute.instances.migrateOnHostMaintenance") AND
log_id("cloudaudit.googleapis.com/system_event") AND
resource.labels.instance_id="<INSTANCE_ID>" AND
severity=INFO
Compute Engine VM terminated/preempted

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
protoPayload.methodName=~"compute\.instances\.(guestTerminate|preempted)" AND
log_id("cloudaudit.googleapis.com/system_event") AND
resource.labels.instance_id="<INSTANCE_ID>"
Compute Engine VM terminated due to scratch disk creation failure

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
protoPayload.serviceName="compute.googleapis.com" AND
(protoPayload.methodName="compute.instances.scratchDiskCreationFailed"
OR
operation.producer:
"compute.instances.scratchDiskCreationFailed") AND
log_id("cloudaudit.googleapis.com/system_event") AND
resource.labels.instance_id="<INSTANCE_ID>" AND
severity=INFO
Compute Engine zone resource pool exhaustion (stockout)

Variables to replace: None

resource.type="gce_instance" AND
log_id("cloudaudit.googleapis.com/activity") AND
(protoPayload.methodName="v1.compute.instances.start" OR
protoPayload.methodName="v1.compute.instances.insert") AND
protoPayload.status.message=~"(ZONE_RESOURCE_POOL_EXHAUSTED|does not have enough resources|resource pool exhausted)" AND
severity>=WARNING
Compute Engine VM instance created

Variables to replace: <INSTANCE_NAME>

resource.type="gce_instance" AND
SEARCH(protoPayload.methodName, "compute.instances.insert") AND
log_id("cloudaudit.googleapis.com/activity") AND
protoPayload.request.name="<INSTANCE_NAME>"
Compute Engine VM instance deleted with name

Variables to replace: <INSTANCE_NAME>

resource.type="gce_instance" AND
SEARCH(protoPayload.methodName, "compute.instances.delete") AND
log_id("cloudaudit.googleapis.com/activity") AND
protoPayload.resourceName:"<INSTANCE_NAME>"
Compute Engine VM instance deleted with ID

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
SEARCH(protoPayload.methodName, "compute.instances.delete") AND
log_id("cloudaudit.googleapis.com/activity") AND
resource.labels.instance_id="<INSTANCE_ID>"
Compute Engine VM instance restarted

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
protoPayload.methodName=~"compute\.instances\.(start|stop|reset|automaticRestart|guestTerminate|instanceManagerHaltForRestart)" AND
(log_id("cloudaudit.googleapis.com/activity")
OR log_id("cloudaudit.googleapis.com/system_event")) AND
resource.labels.instance_id="<INSTANCE_ID>"
Compute Engine Shielded VM boot integrity failure

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
log_id("compute.googleapis.com/shielded_vm_integrity") AND
jsonPayload.earlyBootReportEvent.policyEvaluationPassed="false" AND
resource.labels.instance_id="<INSTANCE_ID>"
Compute Engine VM instance stopped by Guest OS

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
protoPayload.serviceName="compute.googleapis.com" AND
(SEARCH(protoPayload.methodName, "compute.instances.guestTerminate") OR
operation.producer:"compute.instances.guestTerminate") AND
log_id("cloudaudit.googleapis.com/system_event") AND
resource.labels.instance_id="<INSTANCE_ID>" AND
severity=INFO
Compute Engine Shielded VM boot file was blocked

Variables to replace: <INSTANCE_ID>

resource.type="gce_instance" AND
log_id("serialconsole.googleapis.com/serial_port_1_output") AND
textPayload:"Security Violation" AND
resource.labels.instance_id="<INSTANCE_ID>"
Persistent disk created

Variables to replace: <PERSISTENT_DISK_NAME>

resource.type="gce_disk" AND
SEARCH(protoPayload.methodName, "compute.disks.insert") AND
log_id("cloudaudit.googleapis.com/activity") AND
protoPayload.resourceName: "<PERSISTENT_DISK_NAME>"
Nodes added in sole-tenant node

Variables to replace: <NODE_GROUP_ID>

resource.type="gce_node_group" AND
log_id("cloudaudit.googleapis.com/activity") AND
protoPayload.methodName=~("compute.nodeGroups.addNodes"
OR "compute.nodeGroups.insert") AND
resource.labels.node_group_id="<NODE_GROUP_ID>" AND
severity=INFO
Autoscale events in sole-tenant node

Variables to replace: <NODE_GROUP_ID>

resource.type="gce_node_group" AND
log_id("cloudaudit.googleapis.com/system_event") AND
protoPayload.methodName=~("compute.nodeGroups.deleteNodes"
OR "compute.nodeGroups.addNodes") AND
resource.labels.node_group_id="<NODE_GROUP_ID>"
Manual snapshot taken

Variables to replace: <SNAPSHOT_NAME>

resource.type="gce_snapshot" AND
log_id("cloudaudit.googleapis.com/activity") AND
SEARCH(protoPayload.methodName, "compute.snapshots.insert") AND
protoPayload.resourceName:"<SNAPSHOT_NAME>"
Scheduled snapshot taken

Variables to replace: <PERSISTENT_DISK_NAME>

resource.type="gce_disk" AND
log_id("cloudaudit.googleapis.com/system_event") AND
protoPayload.methodName="ScheduledSnapshots" AND
protoPayload.response.operationType="createSnapshot" AND
protoPayload.response.targetLink="<PERSISTENT_DISK_NAME>"
Snapshot schedule created

Variables to replace: <SCHEDULE_NAME>

resource.type="gce_resource_policy" AND
log_id("cloudaudit.googleapis.com/activity") AND
SEARCH(protoPayload.methodName, "compute.resourcePolicies.insert") AND
protoPayload.request.name="<SCHEDULE_NAME>"
Snapshot schedule attached

Variables to replace: <PERSISTENT_DISK_NAME>, <SCHEDULE_NAME>

resource.type="gce_disk" AND
log_id("cloudaudit.googleapis.com/activity") AND
SEARCH(protoPayload.methodName, "compute.disks.addResourcePolicies") AND
protoPayload.request.resourcePolicys:"<SCHEDULE_NAME>" AND
protoPayload.resourceName:"<PERSISTENT_DISK_NAME>"
Quota exceeded

Variables to replace: None

resource.type="gce_instance" AND
SEARCH(protoPayload.methodName, "compute.instances.insert") AND
protoPayload.status.message:"QUOTA_EXCEEDED" AND
severity=ERROR
Query unhealthy instances in instance group

Variables to replace: <INSTANCE_GROUP_NAME>

resource.type="gce_instance_group" AND
resource.labels.instance_group_name="<INSTANCE_GROUP_NAME>" AND
jsonPayload.healthCheckProbeResult.healthState="UNHEALTHY"
Query instance group members within a time frame in UTC time format

Variables to replace: <END_TIME>, <INSTANCE_GROUP_NAME>, <START_TIME>

resource.type="gce_instance_group_manager" AND
resource.labels.instance_group_manager_name="<INSTANCE_GROUP_NAME>" AND
jsonPayload.@type=
"type.googleapis.com/compute.InstanceGroupManagerEvent" AND
jsonPayload.instanceHealthStateChange.detailedHealthState="HEALTHY" AND
timestamp >= "<START_TIME>" AND timestamp <= "<END_TIME>"
Instances added to instance group

Variables to replace: <INSTANCE_GROUP_NAME>

resource.type="gce_instance_group" AND
SEARCH(protoPayload.methodName, "compute.instanceGroups.addInstances") AND
log_id("cloudaudit.googleapis.com/activity") AND
resource.labels.instance_group_name="<INSTANCE_GROUP_NAME>"
Instances removed from instance group

Variables to replace: <INSTANCE_GROUP_NAME>

resource.type="gce_instance_group" AND
SEARCH(protoPayload.methodName, "compute.instanceGroups.removeInstances") AND
log_id("cloudaudit.googleapis.com/activity") AND
resource.labels.instance_group_name="<INSTANCE_GROUP_NAME>"
Instance template set or updated

Variables to replace: <INSTANCE_GROUP_MANAGER>

resource.type="gce_instance_group_manager" AND
log_id("cloudaudit.googleapis.com/activity") AND
protoPayload.methodName=
"v1.compute.instanceGroupManagers.setInstanceTemplate" AND
resource.labels.instance_group_manager_name="<INSTANCE_GROUP_MANAGER>"
Firewall logs

Variables to replace: <INSTANCE_NAME>

resource.type="gce_subnetwork" AND
log_id("compute.googleapis.com/firewall") AND
jsonPayload.instance.vm_name="<INSTANCE_NAME>"

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/cloud-logging-query-generation · 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 or Google.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download cloud-logging-query-generation.zip