hyperpod-issue-report

Collect diagnostic logs and configurations from EKS and Slurm HyperPod clusters.

15|9|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/haozhx23/HyperPod-InstantStart --skill hyperpod-issue-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyperpod-issue-report
Source: https://github.com/haozhx23/HyperPod-InstantStart/tree/main/.claude/skills/hyperpod-issue-report
Command: npx skills add https://github.com/haozhx23/HyperPod-InstantStart --skill hyperpod-issue-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, botocore, pexpect, tarfile, subprocess, json, shutil, tempfile, time, traceback, zipfile, datetime, timezone, argparse, os, platform, concurrent.futures, collections, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the collection of diagnostic logs and configurations from HyperPod clusters, streamlining the process of troubleshooting and AWS Support cases.

Core Features & Use Cases

  • Automated Diagnostic Collection: Collects system and cluster logs, configurations, and other relevant information for troubleshooting and support.
  • EKS and Slurm Support: Functions across both EKS and Slurm orchestrated clusters with auto-detection.
  • Use Case: Ideal for generating comprehensive issue reports for AWS Support or internal investigation, including node failures or performance issues.

Quick Start

Use the hyperpod-issue-report skill to generate a diagnostic report for your HyperPod cluster 'my-cluster'.

Frequently Asked Questions about hyperpod-issue-report

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

FAQPage Schema
How do I collect diagnostic logs from an EKS or Slurm HyperPod cluster for AWS Support?

Automated issue reporting collects system and cluster logs, configurations, and relevant diagnostic data from multiple EKS or Slurm HyperPod nodes in parallel to generate comprehensive reports for AWS Support cases.

What is the best way to automate HyperPod cluster diagnostics and issue reporting?

Automating HyperPod cluster diagnostics involves collecting system logs and configurations across multiple nodes in parallel. This approach auto-detects EKS or Slurm orchestration to streamline troubleshooting and AWS Support case generation.

Do I need Python and boto3 installed to run HyperPod cluster diagnostics?

Yes, collecting HyperPod cluster diagnostics requires Python, boto3, and the SSM agent to be installed and running. These dependencies allow the automated collection process to gather logs and configurations from multiple nodes.

Can I use automated issue reporting for both EKS and Slurm orchestrated HyperPod clusters?

Yes, automated issue reporting supports both EKS and Slurm orchestrated HyperPod clusters. The tool features auto-detection to identify the orchestration type and collect the appropriate diagnostic logs and configurations.

Why does HyperPod diagnostic collection require an SSM agent on the nodes?

The SSM agent is required for HyperPod diagnostic collection because it enables the tool to execute commands remotely and gather system logs, configurations, and other relevant data in parallel from multiple cluster nodes.

When should I run automated issue reporting on my HyperPod cluster?

You should run automated issue reporting when experiencing HyperPod node failures, performance issues, or when you need to generate a comprehensive diagnostic report for AWS Support or internal investigation.