gcp-composer-troubleshooting

Diagnoses failed Cloud Composer DAGs using gcloud logs and remote code to generate RCA reports.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill gcp-composer-troubleshooting-smileafterburn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-composer-troubleshooting
Source: https://github.com/SmileAfterBurn/pani-dumka-ai/tree/main/.gemini/skills/gcp-composer-troubleshooting
Command: npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill gcp-composer-troubleshooting-smileafterburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Cloud Composer (Apache Airflow) DAG fails, finding the root cause requires digging through scattered logs and verifying which code version actually ran. This Skill guides an evidence-based Root Cause Analysis (RCA) workflow so failures are explained with concrete log entries and code references instead of guesswork. ## Core Features & Use Cases - Log-Based Evidence Gathering: Uses gcloud logging read with severity, environment, and DAG ID filters to locate failures and stack traces. - Remote Code Verification: Downloads the actual DAG code from the Composer GCS bucket to ensure analysis targets the running version, not stale local copies. - Structured RCA Reports: Correlates logs with code line numbers, proposes fixes, and generates a saved RCA report. - Use Case: A user reports that the DAG daily_sales_agg failed yesterday at 2pm. The Skill fetches error logs, downloads the remote DAG file, pinpoints a KeyError at line 45, and produces an RCA report with a recommended fix. ## Quick Start Ask the assistant to troubleshoot why your Composer DAG failed and generate a root cause analysis report for a specific DAG ID and time range.

Frequently Asked Questions about gcp-composer-troubleshooting

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

FAQPage Schema
How do I troubleshoot a failed Cloud Composer DAG?▼

Use gcloud logging read with filters like resource.type=cloud_composer_environment, the DAG ID label, and severity>=ERROR to find failure logs. Then download the actual DAG code from the environment's GCS bucket and correlate the traceback with specific code lines.

How to fetch Airflow task logs with gcloud logging?▼

Run gcloud logging read with a filter combining resource.type=cloud_composer_environment, resource.labels.environment_name, labels.dag_id, and severity>=ERROR. Add --limit and a table format with timestamp, severity, task_id, and textPayload for readable output.

Why does my local DAG differ from the one running in Composer?▼

The Composer environment runs code synced to its GCS bucket, which may not match your local files if deployments happened elsewhere. Download the remote DAG with gcloud storage cp and confirm which version to analyze before debugging.

Can this skill automatically fix my broken DAG code?▼

No, it follows a read-only-first approach: it proves the root cause using logs and remote code, then proposes a fix. Code is only modified when the user explicitly asks for the fix to be applied.

What information is needed to start a Composer root cause analysis?▼

Provide the DAG ID, and ideally the Run ID or Task ID and approximate failure time. If you only have a vague error, a time range is enough to search logs and narrow down the failing task.