Merkl Developer Portal logo
get

/v4/analytics/health/ready

Readiness probe — pod runtime snapshot

Always returns HTTP 200. On the public API the body is { status: "OK" }. On the internal instance it 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.

Responses

200
Response for status 200
Schema
object
cpuCoresnumber
cpuQuotaCoresnumber
cpuLimitCoresnumber
cpuLimitBasisenumquotahost
cpuRationumber
requestsInWindownumber
rssBytesnumber
rssRationumber
workingSetBytesnumber
memoryRationumber
maxEventLoopLagMsnumber
windowSecondsnumber
Example
{
  "cpuCores": 0,
  "cpuQuotaCores": 0,
  "cpuLimitCores": 0,
  "cpuLimitBasis": "quota",
  "cpuRatio": 0,
  "requestsInWindow": 0,
  "rssBytes": 0,
  "rssRatio": 0,
  "workingSetBytes": 0,
  "memoryRatio": 0,
  "maxEventLoopLagMs": 0,
  "windowSeconds": 0
}
503
Response for status 503
Schema
object
shuttingDowntrue
required
Example
{
  "shuttingDown": true
}