What problem does it solve? When Cloud TPU training jobs on Google Kubernetes Engine experience sudden throughput drops or step-time regressions (15%+ TPU duty-cycle loss), identifying whether the issue stems from workload resource saturation, hardware throttling, or network fabric faults requires correlating multiple diagnostic sources. This Skill automates that investigation by analyzing ML Diagnostics monitored events and 1-minute Cloud Monitoring metrics to pinpoint the root cause and route remediation accordingly. ## Core Features & Use Cases - ML Diagnostics Workload Monitoring Integration: Query MonitoredEvent analyzer reports (HBM capacity, host memory, CPU utilization, thermal/power throttling, network fabric) to classify performance degradation by category. - System Metrics Correlation: Run PromQL queries over 1-minute Cloud Monitoring metrics (kubernetes_io:node_accelerator_duty_cycle, memory utilization ratios, CPU allocatable utilization) to corroborate analyzer findings. - Instance-to-Node Mapping: Convert Compute Engine instance IDs reported by infrastructure analyzers to GKE node names and physical topology blocks for targeted remediation. - Use Case: A multi-slice JAX training job running on GKE TPUs shows a 20% duty-cycle drop. Use this Skill to determine whether HBM memory is exhausted (requiring batch size reduction), host CPU is saturated (requiring loader optimization), or a TPU node is experiencing thermal throttling (requiring Google Cloud Support escalation). ## Quick Start Provide the project ID, GKE cluster name, workload name, and the timestamp when throughput degradation was observed, then follow the diagnostic workflow to query ML runs, list monitored events, and inspect analyzer reports to route to the correct remediation path.