Health
Liveness probe — pod runtime snapshot
Always returns HTTP 200. The body carries the pod's rolling 60s runtime window — mean cores against the cgroup quota, responses served, RSS against the memory limit, worst event-loop drift. Nothing here fails the probe yet: the thresholds that would identify a GC-bound pod are not calibrated against production traffic, so this ships as telemetry first. Every window is also logged as [RUNTIME] window.
get/v4/health/live
Response
Response for status 200
Changes
No recorded changes to this endpoint across all 3 revisions of this API.