gcp-composer-troubleshooting

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 to correlate the error with the exact failing line.

Gather the DAG ID, run ID, and task ID, retrieve error logs via gcloud logging, and download the remote DAG code with gcloud storage cp. Correlate the stack trace with specific code lines, then document the root cause and proposed fix in an RCA report file.

The remote environment runs the code uploaded to its GCS bucket, which may not match your local files. Always download the remote DAG with gcloud storage cp before analysis, since the remote version is the source of truth for the failure.

No, the skill is read-only by design. It analyzes logs and code to prove the root cause and proposes a fix, but it does not modify code unless you explicitly ask it to apply the fix.

Key commands include gcloud composer environments list, dags list-runs for run history, gcloud logging read for error logs, and gcloud storage cp to download DAG files from the environment bucket for inspection.