The engine PROCESS's resource load — a periodic gauge answering the operator's "what is eating
our CPU". Served at /telemetry/process (see the server's process-load-resource.ts) and read
by the surface. A pure reading with no server-only verdict, so it lives in core, the home of
every shape both sides share.
CPU% is over the tick window (user + system, and can exceed 100% across cores); event-loop lag
is the direct signal for a saturated MAIN THREAD; activeResources approximates the libuv
handles/requests in flight — the "threads" the operator sees.
The engine PROCESS's resource load — a periodic gauge answering the operator's "what is eating our CPU". Served at
/telemetry/process(see the server'sprocess-load-resource.ts) and read by the surface. A pure reading with no server-only verdict, so it lives in core, the home of every shape both sides share.CPU% is over the tick window (user + system, and can exceed 100% across cores); event-loop lag is the direct signal for a saturated MAIN THREAD;
activeResourcesapproximates the libuv handles/requests in flight — the "threads" the operator sees.