troubleshooting-config-items

# Config Item Troubleshooting Skill

## Core Purpose

This skill enables Claude to troubleshoot infrastructure and application configuration items in Mission Control, diagnose health issues, analyze changes, and identify root causes through systematic investigation of config relationships and history.

## Understanding Config Items

A **ConfigItem** represents a discoverable infrastructure or application configuration (Kubernetes Pods, AWS EC2 instances, Azure VMs, database instances, etc.). Each config item contains:

- **health**: Overall health status ("healthy", "unhealthy", "warning", "unknown")
- **status**: Operational state (e.g., "Running", "Stopped", "Pending")
- **description**: Human-readable description (often contains error messages when unhealthy)
- **.config**: The actual JSON specification/manifest (e.g., Kubernetes Pod spec, AWS instance details)
- **type**: The kind of resource (e.g., "Kubernetes::Pod", "AWS::EC2::Instance")
- **tags**: Metadata for filtering and organization
- **parent_id/path**: Hierarchical relationships to other configs
- **external_id**: External system identifier

## Key Workflows

### Initial Investigation

**1. Search and Identify the Config**
Use the MCP `search_catalog` tool to find the config item:

- Search by id, name, type, tags, or other attributes
- Narrow down to the specific config experiencing issues

**2. Get Complete Config Details**
Use the MCP `describe_config` tool to retrieve full config information:

- Review the **health** field for overall status
- Check the **status** field for operational state
- Read the **description** field carefully - this often contains error messages or status information
- Examine the **.config** JSON field - this contains the full specification/manifest

### Change Analysis

**3. Review Recent Changes**
If the issue isn't immediately apparent, use the MCP `search_catalog_changes` tool:

- Get changes for the specific config item
- Look for recent modifications to the specifica