# Health Checks # Health Checks | Field | Value | | --- | --- | | Distribution | BSS — OpenC5ISR | | Product | OpenC5ISR | | Release | 0.15.1 | | Deployment | `openc5isr.bss.dev` | | Source | `/srv/bss/releases/OpenC5ISR-v0.15.0-20app` | | Evidence | Route scan and operational health model | | Source fingerprint | `93926e8c834f1ed79c9017a4096f70c76d73ce4f870f104fbd0cf54b2bed50ee` | | Status | Generated baseline — human review required | > **Verification boundary:** This page combines platform design guidance with static evidence from the release. It does not prove that every detected interface is enabled, reachable, secure, or operational in the deployed environment. ## Candidate health endpoints No route name strongly associated with health/readiness was detected. ## Layered health model | Layer | Check | Good result | | --- | --- | --- | | Process | `systemctl is-active` / container state | Active without restart loop. | | Socket | `ss -lntup` | Expected address/port owned by expected process. | | Local HTTP/API | `curl` loopback endpoint | Expected status/body within threshold. | | Proxy/TLS | `curl` public hostname | Valid certificate, correct routing and headers. | | Dependency | Database/bus/files/knowledge checks | Authenticated dependency response and acceptable latency. | | Workflow | Primary user transaction | End-to-end result is visible, correlated and retained. | ## Health endpoint requirements A liveness endpoint should prove the process can respond; readiness should prove required dependencies and configuration are usable. Do not expose secrets, stack traces or sensitive topology in public health output. --- ## Maintainer Notes Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.