Overview

This skill lists individual error events from Cloud Error Reporting, including stack traces and service context, enabling deep-dive debugging. You can filter by group_id, service, time_range, and limit, and if project isn’t provided the active project from gcp-context is used.

How This Skill Works

It executes the gcloud beta error-reporting events list command with the provided flags and returns a JSON list of error events. If project is omitted, it uses the active project from gcp-context. The output includes details like stack traces and service context for each event.

When to Use It

• Diagnose issues within a specific error group by inspecting recent events.
• Filter by a particular service to isolate failures in that service.
• Triage incidents quickly by listing a small number of recent events (limit).
• Analyze a defined time window using time_range (e.g., 1h, 1d, 30d).
• Obtain raw JSON to feed into automation or dashboards.

Quick Start

1. Step 1: Identify the required group_id (and optional inputs like project, service, limit, time_range).
2. Step 2: Run the gcloud command: gcloud beta error-reporting events list --group-id=[GROUP_ID] --project=[PROJECT] --service=[SERVICE] --limit=[LIMIT] --time-range=[TIME_RANGE] --format=json
3. Step 3: Review the JSON output and inspect stack traces and serviceContext for each event.

Best Practices

• Always provide a valid group_id to target the correct error group.
• Use the optional service filter to narrow down results to a single service.
• Specify time_range to focus on the relevant window and set limit for manageability.
• If possible, set project explicitly or ensure the correct gcp-context is active.
• Use --format=json (or rely on default JSON output) for machine-readable results.

Example Use Cases

• List the latest error events for a known error group within a project.
• Fetch errors for the frontend service with a limit of 50 events.
• Retrieve errors from the last 1 hour to investigate a spike.
• List events for a group without a project to use the active gcp-context.
• Export JSON results for ingestion into a monitoring dashboard.

Frequently Asked Questions