a6-recipe-health-check

Configure active and passive health checks for Apache APISIX upstreams via a6 CLI.

1|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/moonming/a6 --skill a6-recipe-health-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a6-recipe-health-check
Source: https://github.com/moonming/a6/tree/main/skills/a6-recipe-health-check
Command: npx skills add https://github.com/moonming/a6 --skill a6-recipe-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the configuration and monitoring of upstream health checks for Apache APISIX, ensuring high availability and automatically removing unhealthy backend nodes from rotation.

Core Features & Use Cases

  • Active Health Checks: Configure APISIX to periodically probe backend nodes using HTTP, HTTPS, or TCP.
  • Passive Health Checks: Enable APISIX to analyze real traffic responses to detect failures.
  • Combined Checks: Utilize both active and passive checks for robust monitoring.
  • Threshold Configuration: Define healthy/unhealthy criteria based on successes, failures, timeouts, and HTTP status codes.
  • Use Case: Automatically detect and remove failing backend servers from a load balancer pool without manual intervention, ensuring seamless service for users.

Quick Start

Use the a6-recipe-health-check skill to configure active HTTP health checks for an upstream named 'backend' with nodes 'backend-1:8080', 'backend-2:8080', and 'backend-3:8080'.

Frequently Asked Questions about a6-recipe-health-check

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

FAQPage Schema
How do I configure upstream health checks in Apache APISIX?

You can configure upstream health checks in Apache APISIX using the a6 CLI to define active HTTP, HTTPS, or TCP probing and passive traffic analysis thresholds for marking nodes healthy or unhealthy.

What is the difference between active and passive health checks for load balancing?

Active health checks periodically probe backend nodes using HTTP, HTTPS, or TCP requests, while passive health checks analyze real traffic responses to detect failures and automatically remove unhealthy nodes from the load balancing pool.

Can I use both active and passive health checks simultaneously in APISIX?

Yes, you can enable combined checks in APISIX to utilize both active probing and passive real traffic analysis, providing robust monitoring and automatic node management for high availability.

How do I customize healthy and unhealthy thresholds for APISIX upstream nodes?

You can define healthy and unhealthy criteria in APISIX by configuring customizable thresholds based on successes, failures, timeouts, and HTTP status codes to manage upstream nodes automatically.

Does this health check configuration support TCP probing for backend servers?

Yes, the upstream health check configuration supports HTTP, HTTPS, and TCP probing to detect failing backend servers and automatically remove them from the load balancer pool.