/health-check

allowed-tools: Task, Bash(kubectl:*), Bash(docker:*), Bash(curl:*), Bash(jq:*), Bash(systemctl:*), Bash(gdate:*), Bash(rg:*), Bash(fd:*), Read, Write
name: "Health Check"
description: "Comprehensive health monitoring orchestrator with parallel system assessment and automated alerting"
author: "wcygan"
tags: ["ops","infra"]
version: "1.0.0"
created_at: "2025-07-14T00:00:00Z"
updated_at: "2025-07-14T00:00:00Z"

Context

• Session ID: !`gdate +%s%N 2>/dev/null || date +%s%N 2>/dev/null || echo "$(date +%s)$(jot -r 1 100000 999999 2>/dev/null || shuf -i 100000-999999 -n 1 2>/dev/null || echo $RANDOM$RANDOM)"`
• Target system: $ARGUMENTS
• Current directory: !`pwd`
• Kubernetes context: !`kubectl config current-context 2>/dev/null || echo "No K8s context"`
• Docker daemon: !`docker info --format '{{.ServerVersion}}' 2>/dev/null || echo "Docker unavailable"`
• System load: !`uptime | awk '{print $10, $11, $12}' 2>/dev/null || echo "Load unavailable"`
• Available tools: !`echo "kubectl: $(which kubectl >/dev/null && echo ✓ || echo ✗) | docker: $(which docker >/dev/null && echo ✓ || echo ✗) | curl: $(which curl >/dev/null && echo ✓ || echo ✗)"`

**Live System Assessment:**

• **Cluster Status**: !`kubectl get nodes -o json 2>/dev/null | jq -r '.items[]? | "\(.metadata.name): \(.status.conditions[-1].type)"' | head -5 || echo "Kubernetes cluster not accessible"`
• **Container Health**: !`docker ps --format "table {{.Names}}\t{{.Status}}" 2>/dev/null | head -10 || echo "Docker containers not accessible"`
• **Failed Services**: !`systemctl --failed --no-legend 2>/dev/null | wc -l | tr -d ' ' || echo "0"` failed systemd services
• **Resource Usage**: !`free -h 2>/dev/null | awk 'NR==2{print "Memory: " $3 "/" $2}' && df -h / 2>/dev/null | awk 'NR==2{print "Disk: " $3 "/" $2 " (" $5 " used)"}' || echo "Resource info unavailable"`
• **Health Endpoints**: !`curl -s --connect-timeout 3 http://localhost:8080/health 2>/dev/null | jq -r '.status // "Health endpoint unreachable"' || echo "Health endpoint unreachable"`

Your Task

STEP 1: Initialize health monitoring session and analyze system architecture

TRY:

# Initialize session state
echo '{
  "sessionId": "'$SESSION_ID'",
  "targetSystem": "'$ARGUMENTS'",
  "timestamp": "'$(gdate -Iseconds 2>/dev/null || date -Iseconds)'",
  "healthChecks": [],
  "systemComponents": [],
  "monitoringTools": []
}' > /tmp/health-session-$SESSION_ID.json

• ANALYZE system architecture from Context section
• IDENTIFY critical components requiring health monitoring
• DETERMINE monitoring complexity based on infrastructure type
• VALIDATE required tools availability (kubectl, docker, curl are essential)

STEP 2: Comprehensive system discovery using parallel analysis

IF system_complexity == "distributed" OR target_system contains "kubernetes|docker|microservices":

**CRITICAL: Deploy parallel sub-agents for comprehensive health assessment (8-10x faster system analysis)**

IMMEDIATELY launch 8 specialized health monitoring agents:

• **Agent 1: Infrastructure Health Analysis**: Analyze Kubernetes cluster, nodes, networking, and orchestration
• Focus: Pod status, node health, resource allocation, network connectivity, cluster-level services
• Tools: kubectl with JSON output, cluster-level health indicators, network testing, service mesh analysis
• Output: Infrastructure readiness and capacity analysis with resource optimization recommendations

• **Agent 2: Container Ecosystem Health**: Assess Docker containers, images, volumes, and container orchestration
• Focus: Container status, resource usage, health check configurations, image vulnerabilities, volume health
• Tools: docker commands, container inspection, log analysis, image scanning, volume monitoring
• Output: Container ecosystem health and resource utilization with security and performance insights

• **Agent 3: Application Service Health**: Evaluate application-level health endpoints, APIs, and service dependencies
• Focus: HTTP health checks, API availability, service dependencies, response times, error rates
• Tools: curl, API testing, response validation, load testing, dependency mapping
• Output: Application service availability and response metrics with performance optimization recommendations

• **Agent 4: System Resource Monitoring**: Monitor system-level resources, performance, and capacity planning
• Focus: CPU, memory, disk, network utilization and capacity, system performance metrics
• Tools: system monitoring commands, resource analysis, performance profiling, capacity planning
• Output: Resource availability and performance bottlenecks with scaling recommendations

• **Agent 5: Configuration & Alerting Analysis**: Review monitoring and alerting setup, configuration drift
• Focus: Existing monitoring tools, alert configurations, dashboards, configuration management
• Tools: file analysis, configuration validation, alert testing, dashboard analysis
• Output: Current monitoring coverage and improvement opportunities with alerting optimization

• **Agent 6: Security & Compliance Health**: Assess security posture, compliance status, and vulnerability management
• Focus: Security configurations, compliance checks, vulnerability scanning, access controls
• Tools: security scanning, compliance validation, vulnerability assessment, access auditing
• Output: Security health assessment with compliance gaps and vulnerability remediation

• **Agent 7: Performance & Scalability Analysis**: Analyze performance metrics, scalability patterns, and optimization opportunities
• Focus: Performance trends, scalability bottlenecks, resource optimization, load patterns
• Tools: performance monitoring, scalability testing, resource optimization, trend analysis
• Output: Performance insights with scalability recommendations and optimization strategies

• **Agent 8: Operational Readiness Assessment**: Evaluate operational procedures, backup systems, and disaster re