Skip to content

Operations

Health checks

Distinguish gateway liveness from deployment and operation readiness.

Use the deployment gateway's /health route for basic liveness. Readiness and authorization are separate checks.

Check gateway liveness#

GET/health
Shell
curl "$INTEGRITY_GATEWAY_ORIGIN/health"

Use the origin supplied for your deployment. HTTP 200 and status: "ok" indicate that the gateway answered. A db_connected field indicates pool initialization, not a fresh database query.

Check deployment readiness#

Inspect the deployment's readiness and connection capability state before sending traffic. Required review availability, credentials, and authorization are checked for operations independently of liveness. A healthy process does not permit bypassing an unavailable required review.

Check the actual operation#

Health does not prove inference completed or a tool effect happened. Use Runs and the durable operation record to investigate a timeout or disconnect. Keep liveness probes separate from model-quality and end-to-end acceptance tests.