Skip to content
Get packs

Cross-Project Cloud Logging Setup

Set up and troubleshoot Google Cloud centralized logging across multiple projects using gcloud

Source Download skill
Repository
google/skills
Stars
21,782
Licence
Apache-2.0
Files
2 files

What it does

When installed, this skill gives an AI agent a structured playbook for Google Cloud Logging when logs must be gathered from several projects, folders or organizations. The agent can choose between sending all logs to one central log bucket (routing via sinks) or leaving logs where they are and querying them together (read-time aggregation with log scopes), then run the matching gcloud commands. It also sets rules for which commands can run immediately and which need the user's explicit approval because they cost money, change access rights, or discard logs.

Great for

  • Platform or cloud engineers standardizing logging across many Google Cloud projects
  • Teams troubleshooting why logs from one project are not reaching a central bucket
  • Operators who want an agent to draft gcloud commands while keeping approval gates on risky changes

Skip it if

  • Single-project logging setups, which the skill itself says it does not cover
  • Live production changes without review: the agent can run some mutating commands without confirmation (Tier M), and the skill tells it to skip network discovery in sandboxes, so a human should check commands before they touch real projects
  • Users without Google Cloud access or an authenticated gcloud CLI, since the skill cannot work without them

Try asking

  • “Set up a central log bucket in my logging project and route logs from my five source projects into it”
  • “Compare centralized log storage with read-time aggregation for our 200-project organization and recommend one”
  • “Troubleshoot why a log sink from project A to our central bucket is not receiving entries”
  • “Create a log view on the central bucket so the security team only sees audit logs”
Step-by-step guide: how to use Cross-Project Cloud Logging SetupInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the Apache-2.0 licence and an attribution note.

    cloud-logging-cross-project-configuration.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip cloud-logging-cross-project-configuration.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip cloud-logging-cross-project-configuration.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the agent exact project IDs up front; the skill tells it not to run discovery commands and to use placeholders instead, so missing IDs will stall the task
  • Review every command the agent proposes for Tier B (metrics, links, IAM bindings) and Tier D (exclusions, bucket deletion) before approving, since these cost money, change access, or permanently discard logs
  • Ask the agent to explain the centralized versus read-time aggregation trade-off first, especially if you have more than about 375 projects

What's inside

  • references/attribution.md
  • SKILL.md

Redistributed unmodified from google/skills under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.