apache-aiops

Use this skill when a user needs to inspect or diagnose Apache HTTP Server, verify config syntax, inspect parsed virtual hosts and modules, read configured mod_status metrics, an error log or access-log status summary, or perform a guarded graceful reload. It requires local apachectl access.

Apache AIops

Start with apache-aiops diagnose for version, syntax, virtual hosts, modules and optional HTTP status. Use apache-aiops vhosts when a request reaches the wrong site, and apache-aiops config-check when a reload fails. apache-aiops init configures a local target; apache-aiops doctor checks apachectl access.

Read failedProbes, unhealthyProbes, complete and healthy before summarizing results. A completed HTTP probe can report an unhealthy response without a probe error: then unhealthyProbes contains http and healthy is false. healthy is null when HTTP was not configured or the result is incomplete; complete: true alone does not mean the service is healthy. Use config-includes, compiled-modules and static-directives to inspect config sources and build features. The MCP server registers 14 Apache reads, one guarded reload and two governance tools. Reload has dry-run; a returned command is still outcomeUnknown until the target is checked. See guardrails and capabilities.