get

/v4/analytics/health/live

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.

Responses

200
Response for status 200
Schema
object
cpuCoresnumber
required
cpuQuotaCoresnumber
cpuLimitCoresnumber
cpuLimitBasisenumquotahost
cpuRationumber
requestsInWindownumber
required
rssBytesnumber
required
rssRationumber
maxEventLoopLagMsnumber
required
windowSecondsnumber
required
Example
{
  "cpuCores": 0,
  "cpuQuotaCores": 0,
  "cpuLimitCores": 0,
  "cpuLimitBasis": "quota",
  "cpuRatio": 0,
  "requestsInWindow": 0,
  "rssBytes": 0,
  "rssRatio": 0,
  "maxEventLoopLagMs": 0,
  "windowSeconds": 0
}
get
https://analytics.merkl.xyz/v4/analytics/health/live
Merkl Analytics API
curl -X GET "https://analytics.merkl.xyz/v4/analytics/health/live"