Overview

Logs Tail streams live logs for immediate feedback during incidents or deployments. It runs gcloud alpha logging tail with optional filters, project, and buffer-window settings, with JSON formatting recommended for programmatic consumption.

How This Skill Works

It executes: gcloud alpha logging tail [FILTER] --project=[PROJECT] --buffer-window=[BUFFER_WINDOW] --format=json. If project is omitted, it uses the active project from gcp-context. Streaming continues until the specified duration elapses or you interrupt it, delivering JSON-formatted entries when requested.

When to Use It

• During an incident to monitor fresh log entries as they happen
• While validating a deployment rollout and verifying live logs
• When filtering logs for a specific resource, service, or condition
• To inspect logs from a specific project without switching contexts
• When you need a time-bounded live stream (duration) for quick checks

Quick Start

1. Step 1: Identify a filter and optional project (or rely on gcp-context)
2. Step 2: Run the tail command with your filter and options, e.g., gcloud alpha logging tail [FILTER] --project=[PROJECT] --buffer-window=[BUFFER_WINDOW] --format=json
3. Step 3: Stop with Ctrl+C or let the duration end to finish the stream

Best Practices

• Use --format=json for easy programmatic parsing of log entries
• Specify a meaningful filter string to narrow results
• Provide buffer_window to help reorder asynchronous logs
• Rely on the active project from gcp-context if project is not set
• Limit streaming duration to avoid unnecessary resource use and capture only what you need

Example Use Cases

• Tail prod error logs in real-time during an outage with a narrow filter
• Monitor a new deployment's pod logs as it rolls out
• Stream logs for a service using a filter like resource.type and labels
• Capture a 60-second log stream to verify a short-lived incident
• Use in CI/CD to quickly surface relevant logs after a build

Frequently Asked Questions