TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/No-Country-simulation/G9-LATAM-Team-58/llms.txt
Use this file to discover all available pages before exploring further.
/health endpoint probes each of Mindloom’s external dependencies — the inference service and the Oracle database — and returns a structured report of their reachability. Each probe runs concurrently on a virtual thread with a hard 3-second timeout, so a hung or unresponsive dependency can never stall the health check itself. Use this endpoint for liveness and readiness checks in your container orchestration layer, or for monitoring dashboards that need per-service breakdown.
Endpoint
http://localhost:8080Auth: None required
Query parameters: None
How the status is determined
The overallstatus field is computed from the probe results as follows:
UP— the inference probe is reachable AND (the database probe is reachable OR the database is not enabled)DEGRADED— any other combination
db Spring profile), the database probe is skipped entirely. Its entry in dependencies reports enabled: false and does not contribute to the overall UP/DEGRADED decision.
Response — 200 OK
The health endpoint always returns HTTP200, regardless of whether the system is UP or DEGRADED. Check the status field in the body to determine actual health.
Overall system status. Either
"UP" or "DEGRADED". See the logic above for how this value is derived.ISO-8601 UTC timestamp recording when the health check was performed (e.g.
"2026-07-28T10:32:41Z").Array of per-dependency probe results. One entry per dependency — currently
"inference" and "database".Examples
Request
Healthy response (UP)
All dependencies are reachable.
Degraded response (inference down)
The inference probe timed out after 3 seconds.Scaffold mode response (database not configured)
When thedb Spring profile is inactive, the database probe is skipped. If inference is reachable, the overall status is still UP.
Implementation notes
- Both probes run concurrently on virtual threads via
Executors.newVirtualThreadPerTaskExecutor(). A hung probe blocks only its carrier thread and never delays other probes or incoming requests. - The database probe executes
SELECT 1 FROM DUALagainst Oracle to confirm connectivity. - The inference probe calls
IInferenceClient.isReachable(), which hits the inference service’s own/healthendpoint. - The executor is shut down gracefully on application stop via
@PreDestroy.
Error Codes
The endpoint itself does not return error HTTP status codes — it always returns200. Dependency failures are communicated via "reachable": false in the dependencies array and a "DEGRADED" top-level status.