Cloud Logging Query Generation
GoogleOfficialPublished by Google
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- No issues found
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
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/google/cloud-logging-query-generation/downloadUnzip 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
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_instanceresource 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 useresource.labels.instance_nameif that label is available for the resource.Resource Type Accuracy: Do not guess resource types. You must look up the correct
resource.typevalue in the service-specific reference files. For example, useinternal_http_lb_rulefor Internal HTTP(S) Load Balancer rules when filtering by forwarding rule name or region (instead ofhttp_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 omitresource.labels.instance_id="..."if the user didn't specify an instance, but you MUST includelogName=".../projects/<PROJECT_ID>/..."with a placeholder if constructing a regional log bucket query where a project ID is strictly required.
Preferred fields:
Include
resource.typeandlog_idrestrictions 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
Resource Types: Explicitly define the
resource.typein 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
protoPayloadschema paths and common examples.If a specific example is not listed, guess the
protoPayload.methodNameby combining the service and verb. When guessing, you MUST use the scopedSEARCH()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.*orprotoPayload.*field structures when you are certain of their exact name.Use the
SEARCH()function to find the keyword globally within the correctresource.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
- ATTRIBUTION.mdAdded by AutoGineer878 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md8.0 KiB
- references/api_reference.md5.1 KiB
- references/attribution.md1.9 KiB
- references/query_app_engine.md2.2 KiB
- references/query_audit_logs.md8.2 KiB
- references/query_bigquery.md6.2 KiB
- references/query_cloud_functions.md2.0 KiB
- references/query_cloud_observability.md1.4 KiB
- references/query_cloud_run.md1.9 KiB
- references/query_cloud_source_repositories.md229 B
- references/query_cloud_sql.md2.6 KiB
- references/query_cloud_storage.md1.9 KiB
- references/query_cloud_tasks.md202 B
- references/query_compute_engine.md15.5 KiB
- references/query_dataflow.md224 B
- references/query_dataproc.md235 B
- references/query_deployment_manager.md753 B
- references/query_gke.md23.6 KiB
- references/query_iam.md5.7 KiB
- references/query_networking.md7.6 KiB
- references/query_security.md1.4 KiB
- references/query_service_usage.md836 B
- references/query_spanner.md244 B
- references/query_third_party.md4.1 KiB
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
- 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.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download cloud-logging-query-generation.zip