composer/Unhealthy Composer

Diagnose and troubleshoot unhealthy Composer environments.

Product: Cloud Composer Kind: Debugging Tree

Description

This runbook investigates common causes for an unhealthy status in a Cloud Composer environment by analyzing GKE health, resource utilization, and component logs.

step 1 - Check environment health status step 2 - Check for GKE IP exhaustion step 3 - Validate environment service account status step 4 - Check plugins directory existence step 5 - Check web server CPU utilization step 6 - Check for monitoring pod restarts step 7 - Check for snapshot load pod restarts

Executing this runbook

gcpdiag runbook composer/unhealthy-composer \
  -p project_id=value \
  -p name=value \
  -p start_time=value \
  -p end_time=value

Parameters

Name Required Default Type Help
project_id True None str The Project ID of the resource under investigation
name True None str The name of the Composer environment
start_time True None datetime The start time of the environment
end_time True None datetime The end time of the environment

Get help on available commands

gcpdiag runbook --help

Potential Steps