glm-5.1
309878c561
Task graph covers all Phase 1 concerns: config system, TLS termination, proxy handler, operations (rate limiting, logging, health check, admin socket, signals, shutdown, body size limit), deployment artifacts, and two review checkpoints. No circular dependencies. Critical path length of 7. Risk distribution: 3 high-risk (ACME, TLS listener setup, startup orchestration), 7 medium, 11 low, 2 trivial.
2.0 KiB
2.0 KiB
id, name, status, depends_on, scope, risk, impact, level
| id | name | status | depends_on | scope | risk | impact | level | |
|---|---|---|---|---|---|---|---|---|
| ops/health-check | Implement health check endpoint on separate local port and HTTPS fallback | pending |
|
narrow | low | component | implementation |
Description
Implement the health check endpoint on a separate local port (default: 9900, bound to 127.0.0.1 only) and as a fallback on the HTTPS listener.
Local Health Check Port
- Binds to
127.0.0.1:{health_check_port} GET /healthreturns200 OKwith empty bodyhealth_check_port = 0disables the separate listener- Port must not conflict with any listener's
http_portorhttps_porton127.0.0.1(validated in config validation)
HTTPS Health Check Fallback
When the local health check port is enabled, /health is also available on the HTTPS listener(s) for TLS-level health verification. External monitoring should prefer the local health check for liveness and can use the HTTPS endpoint for TLS verification.
What Health Check Verifies
- Process is running and tokio runtime is responsive
- TLS listener is accepting connections (HTTPS endpoint only)
- Config is loaded (StaticConfig and DynamicConfig are initialized)
It does NOT check upstream reachability. The health check answers "is the proxy process healthy?", not "is the upstream reachable?"
Acceptance Criteria
- Local health check binds to
127.0.0.1:{health_check_port}only GET /healthreturns200 OKwith empty bodyhealth_check_port = 0disables the listener- Port conflict detection in config validation
/healthavailable on HTTPS listener(s) as fallback- Health check does not verify upstream reachability
- Integration test: local health check responds 200
- Integration test: HTTPS health check responds 200
References
- docs/architecture/operations.md — health check section
- docs/architecture/decisions/013-health-check-port.md — separate local port rationale
Notes
To be filled by implementation agent
Summary
To be filled on completion