Monitoring & Assurance Managed documentation for Monitoring & Assurance. Health Checks Health Checks Field Value Distribution BSS — OpenSOF Product OpenSOF Release 0.15.1 Deployment opensof.bss.dev Source /srv/bss/releases/OpenSOF-v0.15.0-20app Evidence Route scan and operational health model Source fingerprint cda583b42f2a0d296b268ab5b174932a378c8be6fb52ffa1af14af896e990f6e 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. Logs and Audit Logs and Audit Field Value Distribution BSS — OpenSOF Product OpenSOF Release 0.15.1 Deployment opensof.bss.dev Source /srv/bss/releases/OpenSOF-v0.15.0-20app Evidence Operational logging standard Source fingerprint cda583b42f2a0d296b268ab5b174932a378c8be6fb52ffa1af14af896e990f6e 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. Log sources Source Typical command/location Use systemd/journald journalctl -u --since ... Process lifecycle, stdout/stderr and service errors. Nginx /var/log/nginx/access.log, /var/log/nginx/error.log Routing, status, latency, upstream and TLS symptoms. Application Structured logs or configured log directory Domain events, validation, dependency calls and workflow state. Audit Protected append/central audit store Actor, action, target, policy decision, result and correlation. Sensor/edge Device/agent logs and telemetry Connection, clock, calibration, sample loss and product generation. Required structured fields UTC timestamp plus source clock/host. Severity, service/component, release version and instance. Request/event/task/track/case correlation identifier. Authenticated actor or service identity when applicable. Outcome/error code and safe diagnostic context. Do not log Passwords, API token secrets, private keys, complete authorization headers or session cookies. Sensitive content unless the approved audit/evidence policy explicitly requires and protects it. Unbounded raw sensor/media streams in ordinary application logs. Maintainer Notes Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs. Operational Checklist Operational Checklist Field Value Distribution BSS — OpenSOF Product OpenSOF Release 0.15.1 Deployment opensof.bss.dev Source /srv/bss/releases/OpenSOF-v0.15.0-20app Evidence Operational standard Source fingerprint cda583b42f2a0d296b268ab5b174932a378c8be6fb52ffa1af14af896e990f6e 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. Daily/shift-start checks System time synchronized and no large clock offset alerts. Required services active without restart loops. Disk, memory, CPU and network within operating limits. Public hostnames and local health endpoints respond correctly. OpenBus/data/knowledge/files dependencies reachable. Representative sensor/track/task workflow completes. Backups completed and no unresolved critical security/audit alerts. After any change Configuration syntax validated. Only intended service/process changed. Local, proxy and end-to-end tests passed. Logs reviewed for new warnings/errors. Version/change record and rollback state updated. Handover record Record active release, known degradations, temporary workarounds, open incidents, pending changes, sensor availability, external dependency state and the next required action. Operational continuity should not depend on oral memory. Maintainer Notes Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.