LIVE INSTRUMENTATION // NO STORED HISTORY

STATISTIK PENGUNJUNG

The HUD numbers, with the ruler beside them

This page reads the same instrument the portfolio HUD paints on its WebGL panel: the telemetry endpoint of the process that is serving you right now. Nothing here is stored, averaged overnight, or rounded into a nicer shape.

NO READING — GET /api/telemetry did not answer this cycle

SERVER ROUND TRIP

handler duration (ms)—
samples kept in this process—
go-backend reachable—
postgres ping reported—
backend fetch (ms)—
node heap used (MB)—
runtime node—
runtime next—

ARCHITECTURE TRACE

node = handler duration minus the backend fetch measured inside it; backend = fetch to /api/health; postgres = never measured, the health endpoint answers ok or error without a millisecond figure.

BROWSER FRAME RHYTHM

reports in window—
frames counted—
median frame (ms)—
p95 frame (ms)—
lowest fps—
frames over 33 ms—
top reported resolution—
window opened at—
LAST 6 MINUTES · p95 MEAN PER MINUTEbar = p95 / 33 ms

PROVENANCE

build commit—
response timestamp—

The latency window and the frame window live inside a single Node process, so a second instance keeps its own numbers. Machine identity — build commit, runtimes, heap, the postgres ping — is only sent to a request carrying a valid admin session, so here it is em-dash by design; an empty field is not an old hash or a missing stamp.

HOW EACH FIGURE IS MEASURED

HANDLER DURATIONperformance.now() around the whole GET handler of /api/telemetry, including the backend probe inside it. The last 24 durations are kept, in memory, per Node process.
BACKEND PROBEOne fetch to the go-backend /api/health, aborted after 800 ms. Reachable means it answered at all; the health payload's db field decides OK vs DATABASE ERROR, not the HTTP code.
POSTGRES HOPNever drawn and never numbered. The health endpoint replies ok or error and returns no millisecond figure, so this hop stays empty here and on the WebGL timeline.
FRAME RHYTHMReported by visiting browsers through POST /api/telemetry: fps, median and p95 frame time, frames over 33 ms, and viewport size. The last 120 reports and the last 6 minute buckets are kept; the bucket bars read p95 mean per minute divided by the 33 ms threshold.
RATE LIMITSix reports per minute per IP address, counted in memory. A seventh returns 429 and is not stored.
REFRESHThis page reads the store every 20 seconds and stops while the tab is hidden. A reading that failed erases the previous one instead of staying on screen pretending to be current.

WHAT IS NOT KEPT

The frame window holds numbers only: fps, median, p95, slow-frame count, frames counted and the viewport size they were measured on. No name, no session, no page history and no identity field is accepted — a body carrying anything outside that list is rejected with 400. The IP address is read only as a rate-limit bucket key and is never part of the reported data. Everything above dies with the process.