fix: reduce idle liveness warning noise

This commit is contained in:
Peter Steinberger
2026-05-02 04:55:59 +01:00
parent 16d8dcbcfc
commit c89da2a606
5 changed files with 117 additions and 23 deletions

View File

@@ -114,11 +114,13 @@ export keeps only that a message was omitted and the byte count.
The Gateway records a bounded, payload-free stability stream by default when
diagnostics are enabled. It is for operational facts, not content.
The same diagnostic heartbeat records liveness warnings when the Gateway keeps
The same diagnostic heartbeat records liveness samples when the Gateway keeps
running but the Node.js event loop or CPU looks saturated. These
`diagnostic.liveness.warning` events include event-loop delay, event-loop
utilization, CPU-core ratio, and active/waiting/queued session counts. They do
not restart the Gateway by themselves.
utilization, CPU-core ratio, and active/waiting/queued session counts. Idle
samples stay in telemetry at `info` level; they are only logged as Gateway
warnings when diagnostic work is active, waiting, or queued. They do not
restart the Gateway by themselves.
Inspect the live recorder: