GET /health
Comprehensive health check endpoint that verifies API and InfluxDB connectivity.Response
System health status:
healthy, degraded, or unhealthyDatabase status:
connected, mock, or unavailableHuman-readable status description
Example
cURL
Response (Healthy)
Response (Mock Mode)
Response (Degraded)
Status Codes
200- Health check succeeded (even in mock/degraded mode)503- Critical failure (rare, only if API itself is unresponsive)
The
/health endpoint returns 200 even in mock mode. This is intentional - the system uses graceful degradation to allow demo/testing without a live InfluxDB instance.GET /ping
Lightweight heartbeat endpoint with no database or ML dependencies. Used by the frontend’s keep-alive mechanism to prevent Render free-tier cold starts.Response
Always returns
okExample
cURL
Response
Status Codes
200- Pong received
Keep-Alive Strategy
The frontend dashboard sends a/ping request every 10 minutes to keep the Render backend warm:
Comparison
| Endpoint | Database Check | ML Check | Use Case | Latency |
|---|---|---|---|---|
/health | ✅ Yes | ❌ No | Deployment verification, admin dashboards | ~50-200ms |
/ping | ❌ No | ❌ No | Keep-alive, uptime monitoring | 1ms |
/health for comprehensive status checks before deployments. Use /ping for lightweight heartbeats.