cloud-logging-cross-project-configuration

Configure cross-project centralized logging and read-time log aggregation on Google Cloud.

19.1k|1.5k|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/google/skills --skill cloud-logging-cross-project-configuration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-logging-cross-project-configuration
Source: https://github.com/google/skills/tree/main/skills/cloud/cloud-logging-cross-project-configuration
Command: npx skills add https://github.com/google/skills --skill cloud-logging-cross-project-configuration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing logs scattered across many Google Cloud projects makes querying, access control, and analytics difficult. This Skill guides you through centralizing log storage in one project or aggregating logs at query time, with built-in safety tiers for risky operations.

Core Features & Use Cases

  • Centralized Log Routing: Create log buckets, sinks, and custom log views to route logs from multiple projects, folders, or organizations into a single regional log bucket.
  • Read-Time Aggregation with Log Scopes: Configure log scopes and observability scopes to query logs stored across up to 100 views without duplicating data.
  • Safety-Tiered Command Execution: Classifies gcloud commands into read-only, mutation, billing/security-sensitive, and destructive tiers with appropriate confirmation requirements.
  • Use Case: A platform team needs audit-ready centralized logging for 50 projects. The Skill walks them through creating a central bucket, organization-level sinks with audit-log exclusions, IAM writer identity grants, and verification queries.

Quick Start

Ask the agent to set up centralized logging that routes logs from your source projects into a central log bucket in a designated Google Cloud project.

Frequently Asked Questions about cloud-logging-cross-project-configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I centralize logs from multiple Google Cloud projects?

Create a regional log bucket in a central project, then create log sinks in each source project, folder, or organization pointing to that bucket. Grant each sink's writer identity the logging.bucketWriter or logging.logWriter role on the central project.

What is the difference between centralized log storage and log scopes?

Centralized storage routes all logs into one bucket, scaling to thousands of projects and simplifying SQL analytics. Log scopes aggregate logs at query time across up to 100 views, avoiding data duplication but requiring IAM access on every source project.

Why are logs not appearing in my central log bucket?

The most common cause is missing IAM permissions: the sink's writer identity must be granted logging.bucketWriter on the central project. Also verify sink filters use LOG_ID("name") syntax and that no exclusion filter discards the logs.

Can I query logs across projects without copying them?

Yes, use log scopes for read-time aggregation. Create a log scope in a scoping project listing up to 100 log views from source projects, then optionally link it to the default observability scope for Logs Explorer.

When should I not use cross-project centralized logging?

Avoid it for single-project basic configurations, and be aware it can duplicate storage costs if exclusions are not set. For fewer than 375 projects where cost matters, read-time aggregation with log scopes is often more cost-effective.