Wire API health JSON into Ops Portal (servers page)
This commit is contained in:
+3
-1
@@ -118,5 +118,7 @@
|
|||||||
- Script: `/root/.hermes/scripts/api-health-check.py` (probes all 41 internal endpoints)
|
- Script: `/root/.hermes/scripts/api-health-check.py` (probes all 41 internal endpoints)
|
||||||
- Watchdog: cron job `35f99c362658` runs every 30 min, alerts Telegram only when something is down
|
- Watchdog: cron job `35f99c362658` runs every 30 min, alerts Telegram only when something is down
|
||||||
- JSON state: `/var/log/api-health/api-health.json`
|
- JSON state: `/var/log/api-health/api-health.json`
|
||||||
- Coverage: 41 endpoints across Core, app1, app2, app3 (verified 41/41 up on 2026-07-31)
|
- Ops Portal: `GET /api/api-health` (auth required) serves the JSON snapshot; Servers page shows "API Health" card with per-endpoint up/down + latency, auto-refreshes every 60s with the page
|
||||||
|
- Coverage: 41 endpoints across Core, app1, app2, app3 (verified 41/41 up on 2026
|
||||||
|
7: 31)
|
||||||
- Note: localhost-bound services on remote hosts are probed via SSH (`ssh root@host curl 127.0.0.1:PORT`); Grafana is on :3002 not :3000; Wazuh dashboard is HTTPS-only.
|
- Note: localhost-bound services on remote hosts are probed via SSH (`ssh root@host curl 127.0.0.1:PORT`); Grafana is on :3002 not :3000; Wazuh dashboard is HTTPS-only.
|
||||||
|
|||||||
Reference in New Issue
Block a user