技能檔案

A6 Recipe Health Check

Name: A6 Recipe Health Check
Author: api7

Recipe skill for configuring upstream health checks using the a6 CLI. Covers active health checks (HTTP probing), passive health checks (response analysis), combining both, configuring healthy/unhealthy thresholds, and monitoring upstream node status.

api70 星標2026年3月7日

職業
分類: 除錯

技能內容

Overview

Health checks monitor upstream backend nodes and automatically remove unhealthy nodes from the load balancer pool. APISIX supports two types:

Active: APISIX periodically probes each node with HTTP/HTTPS/TCP requests
Passive: APISIX analyzes real traffic responses to detect failures

Use both together for the most robust setup.

When to Use

Automatically remove failing backend nodes from rotation
Detect and recover from backend failures without manual intervention
Ensure high availability across multiple backend instances
Monitor backend health status via the a6 CLI

Health Check Configuration Reference

Active Health Check

Field	Type	Default	Description

相關技能

A6 Recipe Health Check | Skills Pool

Field	Type	Default	Description
`checks.passive.type`	string	`"http"`	Check type: `"http"`, `"https"`, or `"tcp"`
`checks.passive.healthy.successes`	integer	`5`	Consecutive successes to mark healthy
`checks.passive.healthy.http_statuses`	array[integer]	`[200, 201, 202, ..., 399]`	HTTP codes considered healthy
`checks.passive.unhealthy.http_failures`	integer	`5`	Consecutive failures to mark unhealthy
`checks.passive.unhealthy.tcp_failures`	integer	`2`	Consecutive TCP failures to mark unhealthy
`checks.passive.unhealthy.timeouts`	integer	`7`	Consecutive timeouts to mark unhealthy
`checks.passive.unhealthy.http_statuses`	array[integer]	`[429, 500, 503]`	HTTP codes considered unhealthy

a6 upstream create -f - <<'EOF'
{
  "id": "backend",
  "type": "roundrobin",
  "nodes": {
    "backend-1:8080": 1,
    "backend-2:8080": 1,
    "backend-3:8080": 1
  },
  "checks": {
    "active": {
      "type": "http",
      "http_path": "/health",
      "healthy": {
        "interval": 5,
        "successes": 2,
        "http_statuses": [200]
      },
      "unhealthy": {
        "interval": 3,
        "http_failures": 3,
        "http_statuses": [500, 502, 503]
      }
    }
  }
}
EOF

a6 upstream create -f - <<'EOF'
{
  "id": "backend-passive",
  "type": "roundrobin",
  "nodes": {
    "backend-1:8080": 1,
    "backend-2:8080": 1
  },
  "checks": {
    "passive": {
      "type": "http",
      "unhealthy": {
        "http_failures": 3,
        "http_statuses": [500, 502, 503],
        "timeouts": 3
      },
      "healthy": {
        "successes": 5,
        "http_statuses": [200, 201, 202, 203, 204]
      }
    }
  }
}
EOF

a6 upstream create -f - <<'EOF'
{
  "id": "production-backend",
  "type": "roundrobin",
  "nodes": {
    "backend-1:8080": 1,
    "backend-2:8080": 1,
    "backend-3:8080": 1
  },
  "checks": {
    "active": {
      "type": "http",
      "http_path": "/health",
      "healthy": {
        "interval": 5,
        "successes": 2,
        "http_statuses": [200]
      },
      "unhealthy": {
        "interval": 2,
        "http_failures": 3,
        "timeouts": 2,
        "http_statuses": [500, 502, 503, 504]
      }
    },
    "passive": {
      "type": "http",
      "unhealthy": {
        "http_failures": 3,
        "http_statuses": [500, 502, 503],
        "timeouts": 3
      },
      "healthy": {
        "successes": 3,
        "http_statuses": [200, 201, 204]
      }
    }
  }
}
EOF

# View health status of all nodes
a6 upstream health backend

{
  "checks": {
    "active": {
      "type": "tcp",
      "healthy": {
        "interval": 5,
        "successes": 2
      },
      "unhealthy": {
        "interval": 2,
        "tcp_failures": 3,
        "timeouts": 2
      }
    }
  }
}

{
  "checks": {
    "active": {
      "type": "https",
      "http_path": "/health",
      "https_verify_certificate": true,
      "healthy": {
        "interval": 10,
        "successes": 2,
        "http_statuses": [200]
      },
      "unhealthy": {
        "interval": 5,
        "http_failures": 3
      }
    }
  }
}

{
  "checks": {
    "active": {
      "type": "http",
      "http_path": "/internal/health",
      "host": "health.internal",
      "req_headers": [
        "Authorization: Bearer health-check-token",
        "X-Health-Check: true"
      ],
      "healthy": {
        "interval": 10,
        "successes": 2
      },
      "unhealthy": {
        "interval": 5,
        "http_failures": 3
      }
    }
  }
}

{
  "checks": {
    "active": {
      "type": "http",
      "http_path": "/health",
      "timeout": 2,
      "healthy": {
        "interval": 3,
        "successes": 1
      },
      "unhealthy": {
        "interval": 1,
        "http_failures": 1,
        "timeouts": 1
      }
    }
  }
}

`checks.active.type`	string	`"http"`	Check type: `"http"`, `"https"`, or `"tcp"`
`checks.active.http_path`	string	`"/"`	HTTP path to probe
`checks.active.host`	string	—	Host header for HTTP probes
`checks.active.port`	integer	—	Override port for probing (default: use node port)
`checks.active.timeout`	number	`1`	Probe timeout in seconds
`checks.active.concurrency`	integer	`10`	Number of concurrent probes
`checks.active.https_verify_certificate`	boolean	`true`	Verify TLS certificate for HTTPS probes
`checks.active.req_headers`	array[string]	—	Additional request headers for probes
`checks.active.healthy.interval`	integer	`1`	Seconds between probes for healthy nodes
`checks.active.healthy.successes`	integer	`2`	Consecutive successes to mark node healthy
`checks.active.healthy.http_statuses`	array[integer]	`[200, 302]`	HTTP codes considered healthy
`checks.active.unhealthy.interval`	integer	`1`	Seconds between probes for unhealthy nodes
`checks.active.unhealthy.http_failures`	integer	`5`	Consecutive HTTP failures to mark unhealthy
`checks.active.unhealthy.tcp_failures`	integer	`2`	Consecutive TCP failures to mark unhealthy
`checks.active.unhealthy.timeouts`	integer	`3`	Consecutive timeouts to mark unhealthy
`checks.active.unhealthy.http_statuses`	array[integer]	`[429, 404, 500, 501, 502, 503, 504, 505]`	HTTP codes considered unhealthy

A6 Recipe Health Check

Overview

When to Use

Health Check Configuration Reference

Active Health Check

A6 Recipe Health Check

Overview

When to Use

Health Check Configuration Reference

Active Health Check

Passive Health Check

Step-by-Step: Configure Health Checks

1. Active HTTP health check

2. Passive health check (analyze real traffic)

3. Combined active + passive (recommended for production)

4. Check upstream health status

Common Patterns

TCP health check (non-HTTP services)

HTTPS health check with certificate verification

Custom probe headers (for auth-protected health endpoints)

Aggressive unhealthy detection (fast failover)

Config Sync Example

Session Logs

OpenClaw Test Heap Leaks

Node Connect

Openclaw Qa Testing

Openclaw Secret Scanning Maintainer

Flags