Readiness probe — pod runtime snapshot
Changed onAlways 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.
Request
- Base URL: https://api.merkl.xyz (the document declares no server; this is the origin it was published from)
- URL: https://api.merkl.xyz/v4/health/ready
- Auth: apiKey (a scheme the document does not define)
Response
Response for status 200
Changes
- info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- info
- breaking
the response's body type changed from
objectto no type for status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - info
added
subschema #1subschema #2to the response bodyanyOflist for the response status
- breaking