Skip to main content
A function health check is implemented by your application, not by the Edge Compute control-plane API. The scaffolded TypeScript and JavaScript entrypoints answer /health before other routing:
Keep this route dependency-free — no KV reads and no outbound calls — so an external checker can distinguish “function down” from “dependency down”. In Go and Python, add an equivalent route yourself. HTTP is the function trigger, so probing is external by design. Point an uptime monitor or scheduled job at your deployed function’s health URL:
/health is therefore documentation for a recommended function-owned route. It is not part of the Edge Compute Observability REST API.