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
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.
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).
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.
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:
- App Engine
- BigQuery
- Cloud Deployment Manager
- Cloud Functions
- Cloud Observability (Monitoring, Logging, Trace)
- Cloud Run
- Cloud Source Repositories
- Cloud Spanner
- Cloud SQL
- Cloud Storage
- Cloud Tasks
- Compute Engine (GCE)
- Dataflow
- Dataproc
- Kubernetes Engine (GKE)
- IAM & Service Accounts
- Networking (VPC, Load Balancing, and others)
- Security (Audit logging)
- Service Usage (Enable/Disable API, Quotas)
- Third Party (for example, Nginx, Apache)
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
- 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")).
- 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".
- 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
1---2description: 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.3metadata:4 source: https://skillmd.com/skills/h3y6e/cloud-logging-query-generation5 category: CloudObservabilityAndMonitoring6 github-path: skills/cloud/cloud-logging-query-generation7 github-ref: refs/heads/main8 github-repo: https://github.com/google/skills9 github-tree-sha: 75a8a3a86114c1ade309683b28bbe8816627826810 version: 1.0.211name: cloud-logging-query-generation12---1314# Generate Logging Query Language queries1516Use this skill to generate correct Logging Query Language (LQL) queries for17Cloud Logging.1819## Attribution2021**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you22MUST read [Usage Attribution](references/attribution.md). For commands executed23directly in the terminal (never in generated scripts, Terraform, or user code),24prefix `gcloud` with25`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:cloud-logging-query-generation)"`26and append `agent-skills/1.0 (skill:cloud-logging-query-generation)` to `User-Agent` headers.2728## Core rules29301. **Strict syntax requirements:**3132 * **Always use double quotes (`"`)** for string literals. Do not use33 single quotes (`'`).34 * Write boolean operators in all capitals: `AND`, `OR`, `NOT`.35 * Always use parentheses to group terms and explicitly enforce precedence.36372. **Common pitfalls:**3839 * **Instance ID vs. Instance Name:** For the `gce_instance` resource type,40 do NOT compare instance names to instance IDs. Instance names are41 strings (for example, `my-instance`). Instance IDs are numeric. If you42 only have the name, then search by instance name,43 `SEARCH("my-instance")`, or use `resource.labels.instance_name` if that44 label is available for the resource.45 * **Resource Type Accuracy:** Do not guess resource types. You must look46 up the correct `resource.type` value in the service-specific reference47 files. For example, use `internal_http_lb_rule` for Internal HTTP(S)48 Load Balancer rules when filtering by forwarding rule name or region49 (instead of `http_load_balancer`).50513. **Output format and placeholders:**5253 * Output **only** the raw LQL query text. Do not include conversational54 filler. Do not wrap the query in markdown code blocks unless explicitly55 requested by the user. Valid LQL comments (using `--`) are allowed, and56 are the ONLY acceptable way to include explanations or warnings.57 * **Never block on missing variables.** If the user's request lacks58 specific identifiers (like a project ID, instance name, or IP address),59 do not ask them for clarification. If the variable is required for a60 functional query (like a log bucket name for a regional log), insert an61 uppercase placeholder string wrapped in angle brackets (for example,62 `"<PROJECT_ID>"`). **CRITICALLY**: If you include a placeholder for a63 variable the user omitted, it will act as an explicit filter that causes64 logs to be missed. Therefore, you MUST omit the entire filter/line65 containing the placeholder if the field is not strictly required. For66 example, completely omit `resource.labels.instance_id="..."` if the user67 didn't specify an instance, but you MUST include68 `logName=".../projects/<PROJECT_ID>/..."` with a placeholder if69 constructing a regional log bucket query where a project ID is strictly70 required.71724. **Preferred fields:**7374 * Include `resource.type` and `log_id` restrictions when the query targets75 specific Google Cloud services or resources. Global queries (for76 example, "latest error logs") do not require these restrictions.7778## Detailed reference7980Refer to `references/api_reference.md` for LQL syntax rules, including81Operators, NULL handling, SEARCH, and Regex.8283## Service reference files8485Before generating a query, you MUST read the examples for the specific service.86LQL schemas and `resource.type` values are service-specific. **Do not stop87reading after finding the Base Schema in the file. You must verify if there are88specific requirements for state tracking (like `previousState`) or89resource-specific log IDs detailed in the paragraphs or specific query examples90below the schema block.**9192**For the following services, read the exact file listed:**9394* [App Engine](references/query_app_engine.md)95* [BigQuery](references/query_bigquery.md)96* [Cloud Deployment Manager](references/query_deployment_manager.md)97* [Cloud Functions](references/query_cloud_functions.md)98* [Cloud Observability (Monitoring, Logging, Trace)](references/query_cloud_observability.md)99* [Cloud Run](references/query_cloud_run.md)100* [Cloud Source Repositories](references/query_cloud_source_repositories.md)101* [Cloud Spanner](references/query_spanner.md)102* [Cloud SQL](references/query_cloud_sql.md)103* [Cloud Storage](references/query_cloud_storage.md)104* [Cloud Tasks](references/query_cloud_tasks.md)105* [Compute Engine (GCE)](references/query_compute_engine.md)106* [Dataflow](references/query_dataflow.md)107* [Dataproc](references/query_dataproc.md)108* [Kubernetes Engine (GKE)](references/query_gke.md)109* [IAM & Service Accounts](references/query_iam.md)110* [Networking (VPC, Load Balancing, and others)](references/query_networking.md)111* [Security (Audit logging)](references/query_security.md)112* [Service Usage (Enable/Disable API, Quotas)](references/query_service_usage.md)113* [Third Party (for example, Nginx, Apache)](references/query_third_party.md)114115**For Google Cloud services that aren't listed:** If the service is not listed116above, write the LQL query based on your general knowledge.117118## Query generation rules1191201. **Resource Types:** Explicitly define the `resource.type` in your queries121 when focusing on specific services. For some queries, you may need to search122 across multiple types (for example, `resource.type=("bigquery_project" OR123 "bigquery_dataset")`).1242. **Audit and Admin Logs:** If the user asks for audit logs, admin logs, API125 logs, or logs about who created, updated, deleted, read, or accessed a126 resource:127 * You MUST read128 [references/query_audit_logs.md](references/query_audit_logs.md) for the129 correct `protoPayload` schema paths and common examples.130 * If a specific example is not listed, guess the `protoPayload.methodName`131 by combining the service and verb. When guessing, you MUST use the132 scoped `SEARCH()` function (e.g., `SEARCH(protoPayload.methodName,133 "compute.instances.insert")`) instead of the exact match operator (`=`)134 to avoid version prefix mismatches. Do NOT use the colon operator (`:`)135 as it may cause substring false positives.136 * For generic API enable/disable events (e.g., a service was disabled),137 always use `resource.type="audited_resource"`.1383. **Handling Unknown Schemas (Crucial):** If the user asks to filter by a139 specific field or condition, and if you cannot find a matching example or140 schema in the reference files, **then you must generate a query using global141 search.**142 * Only specify `jsonPayload.*` or `protoPayload.*` field structures when143 you are certain of their exact name.144 * Use the `SEARCH()` function to find the keyword globally within the145 correct `resource.type`.146 * **Mandatory LQL Comment:** When delivering a query that uses `SEARCH`,147 you MUST add an LQL comment (using `--`) at the top of the query148 indicating you used a global keyword search because the exact schema149 wasn't in your references. Do NOT output conversational text, strictly150 adhere to the Output Format rule.151152## Supporting links153154* [Cloud Logging query language documentation](https://docs.cloud.google.com/logging/docs/view/logging-query-language)155* [Monitored resource types catalog](https://docs.cloud.google.com/logging/docs/api/v2/resource-list)156* [Cloud Logging query library](https://docs.cloud.google.com/logging/docs/view/query-library)