troubleshoot-apache-httpd

What problem does it solve?

Apache HTTPD failures are often hard to diagnose because symptoms can look similar (server “down”, timeouts, rising errors, or zero throughput), but the root cause differs by failure archetype like worker exhaustion, memory exhaustion, listen queue overflow, slow backend cascades, or log disk full/pipe stalls.

Core Features & Use Cases

• Signal-driven triage with MCP: Queries Netdata via MCP to confirm the Apache HTTPD process presence, critical-path reachability, throughput/latency signals, and request/error behavior.
• Operator playbook diagnostic tree: Routes an AI through the same domain-by-domain failure patterns (Availability, Throughput, Latency, Errors, Saturation, Resource Utilization) using dedicated rule files.
• Verification-ready remediation loop: Recommends remediation aligned to the matching failure archetype and provides a “re-run the same MCP queries” verification approach to confirm the signal returns to expected bands.

Quick Start

Use this skill when diagnosing an Apache HTTPD incident and ask the agent to triage worker exhaustion or listen queue overflow using MCP queries against the Netdata contexts for apache HTTPD.