vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 13:30:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: quiet nonblocking diagnostic logs

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-03 19:24:23 +01:00
parent 01e2755dc3
commit 2b7e8dacd3
4 changed files with 59 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/gateway/diagnostics.md
View File

@@ -118,9 +118,11 @@ 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. 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.
samples stay in telemetry at `info` level. Liveness samples become Gateway
warnings only when work is waiting or queued, or when active work overlaps with
sustained event-loop delay. Transient max-delay spikes during otherwise healthy
background work stay in debug logs. They do not restart the Gateway by
themselves.
Inspect the live recorder: