{"ref":"capability:health-checks","page":"/capabilities/health-checks","json":"/capabilities/health-checks.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"health-checks","name":"Health checks","domain":"operations-and-runtime","ecosystems":["cap"],"universal":true,"description":"Readiness and liveness that mean something for a service — is the database reachable, are bindings resolved, is the message broker connected — rather than merely whether the process is up.","short":"Readiness and liveness checks that mean something for a service","core_coverage":{"state":"core-only","what_core_does":"Node.js answers /health with 200 and {status:'UP'}. Java configures separate liveness and readiness probes via cds add mta or cds add kyma.","where_it_stops":"It stops at whether the process is up. Nothing checks whether the service can actually serve — database reachable, bindings resolved, broker connected — so the endpoint stays green while the application is unable to do its job.","sources":[{"url":"https://cap.cloud.sap/docs/guides/deploy/health-checks","title":"Health Checks","checked":"2026-08-31"},{"url":"https://cap.cloud.sap/docs/guides/deploy/health-checks","title":"Health Checks — capire","checked":"2026-09-27","quote":"For CAP Node.js, the runtime provides an out-of-the-box endpoint for liveness and readiness checks at /health."},{"url":"https://cap.cloud.sap/docs/guides/deploy/health-checks","title":"Health Checks — capire","checked":"2026-09-27","quote":"For CAP Java, cds add mta and cds add kyma add the necessary dependencies and configuration for the publicly available probe endpoints /actuator/health/liveness and /actuator/health/readiness."}],"assessed_at":"2026-09-27"},"history":[{"date":"2026-08-31","field":"core_coverage.state","from":"unmapped","to":"left-open-on-purpose","reason":"capire documents an out-of-the-box /health endpoint. The gap is shallower than claimed: the core answers liveness, not readiness of dependencies."},{"date":"2026-08-31","field":"core_coverage.state","from":"left-open-on-purpose","to":"core-and-community","reason":"States renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately."},{"date":"2026-09-27","field":"core_coverage","from":"without the runtime's page","to":"cites the runtime's page","reason":"P1 backfill 2026-09-27: the paragraph and the runtime edge now rest on a page in common."},{"date":"2026-10-17","field":"description","from":"Readiness and liveness that mean something for a CAP service — is the database reachable, are bindings resolved, is the message broker connected — rather than merely whether the process is up.","to":"Readiness and liveness that mean something for a service — is the database reachable, are bindings resolved, is the message broker connected — rather than merely whether the process is up.","reason":"Keep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit."},{"date":"2026-10-26","field":"core_coverage.state, core_coverage.relationship","from":"core-and-community (narrow-by-design)","to":"core-only (relationship removed)","reason":"Reassessed against the graph (check:capabilities): the only provider behind the CAP door is the runtime core @sap/cds, so no provider of another origin counts for the door. The state follows the providers; the block's prose already names no community answer."}],"drafted_with_ai":true,"framing_by_ecosystem":{"cap":{"description":"Readiness and liveness that mean something for a CAP service — is the database reachable, are bindings resolved, is the message broker connected — rather than merely whether the process is up."}}},"sap_delivery":{"door":"cap","all":{"built_in":[{"ref":"artifact:sap-cds","name":"@sap/cds","json":"/artifacts/sap-cds.json"}],"documented_pattern":[],"announced":[],"packages":[]},"by_flavor":{"node":{"built_in":[{"ref":"artifact:sap-cds","name":"@sap/cds","json":"/artifacts/sap-cds.json"}],"documented_pattern":[],"announced":[],"packages":[]},"java":null}},"edges":{"use_cases":[],"shared_tasks":[],"related_tasks":[],"options":[{"ref":"artifact:sap-cds","name":"@sap/cds","json":"/artifacts/sap-cds.json","ecosystem":"cap","origin_ring":"sap-official"}],"samples":[],"explained_by":[{"ref":"content:btp-sapcap-quirky-nuggets-n05-n06","name":"#BTP #SAPCAP: Quirky Nuggets (N05-N06)","json":"/content/btp-sapcap-quirky-nuggets-n05-n06.json"}],"normative_context":[]}}