openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@c89da2a606

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-05-02 04:00:00 +00:00
parent 7e29b77fdf
commit 38e262c095
2 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "42cdd0bdf44e8ab85108d46e5eb177e95bc713cf",
"syncedAt": "2026-05-02T03:44:07.857Z"
"sha": "c89da2a60679a87ae8590f4cd9c590cfd08acc62",
"syncedAt": "2026-05-02T03:58:10.416Z"
}

8
docs/gateway/diagnostics.md
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: