Real boundary checks
Health and readiness endpoints, identity authorities, the public site, and unauthenticated request rejection are verified—not inferred from a process being online.
Independent checks exercise the same public website, APIs, login redirects, and fail-closed request boundary customers reach. This page never relies on an operator manually declaring the system healthy.
Health and readiness endpoints, identity authorities, the public site, and unauthenticated request rejection are verified—not inferred from a process being online.
Repeated degradation, monitor failures, missing heartbeats, and exhausted retries produce separate operator alarms with recovery notifications.
The public artifact contains component state, observation time, and latency only. It excludes URLs, provider responses, tenant data, request bodies, and internal identifiers.
These synthetic checks complement application alarms and release acceptance. Contracted uptime, support targets, data residency, and customer-specific deployment commitments are documented in the applicable agreement.