troubleshooting-health-checks

Diagnose Mission Control health check failures by analyzing configurations and failure patterns.

Updated Nov 12, 2025
One-click install
npx skills add https://github.com/flanksource/claude-code-plugin --skill troubleshooting-health-checks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting-health-checks
Source: https://github.com/flanksource/claude-code-plugin/tree/main/skills/health
Command: npx skills add https://github.com/flanksource/claude-code-plugin --skill troubleshooting-health-checks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Health checks are critical for monitoring system status, but debugging their failures can be complex and time-consuming. This Skill automates the analysis of health check configurations and historical data to quickly pinpoint root causes, saving engineers valuable time.

Core Features & Use Cases

  • Failure Pattern Analysis: Automatically identify if health check failures are intermittent, consistent, or time-based, providing insights into underlying issues.
  • Configuration Cross-Reference: Analyze health check configurations against failure patterns to identify misconfigurations or insufficient thresholds.
  • Diagnostic Summary: Generate a clear summary of the problem, including root cause, contributing factors, and impact assessment.
  • Use Case: A critical API health check is intermittently failing. Use this Skill to analyze its history, identify network instability as the cause, and recommend a more resilient configuration.

Quick Start

Troubleshoot the health check named 'api-status' in Mission Control.

Frequently Asked Questions about troubleshooting-health-checks

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

FAQPage Schema
How do I troubleshoot a health check that's failing intermittently?

Troubleshoot intermittent health check failures by analyzing historical execution patterns to distinguish between consistent outages, transient issues, and time-based triggers. This Skill examines check configurations and failure timelines to identify root causes like network instability or threshold misconfigurations.

What causes health checks to timeout, and how do I fix them?

Health check timeouts stem from configuration issues, resource constraints, or network delays. Diagnose timeouts by cross-referencing your check settings against execution history and failure patterns, then validate corrected configurations with live test runs.

Can I automate the process of identifying health check misconfigurations?

Yes. Automated health check diagnostics analyze configurations against historical failure data to pinpoint misconfigurations, insufficient thresholds, and contributing factors without manual log review.

How do I determine if a health check failure is a real outage or a false positive?

Distinguish real outages from false positives by analyzing failure pattern frequency, timing consistency, and correlation with configuration settings. This provides clear diagnostics to separate genuine issues from check logic problems.

What should I check when a critical health check starts failing?

When a critical check fails, examine its configuration accuracy, review recent catalog changes, analyze failure history for patterns, and validate the check against live system state to pinpoint the root cause.