Skip to content

Node diagnostics

These read-only views open from a selected node in :nodes — none is a standalone top-level command. For a server-side, streaming cluster readiness check (not node-scoped), see :healthcheck. Each is scoped to the node the view was opened for, and r re-fetches that same node rather than whatever is currently selected back in :nodes. Press Esc or q to return to :nodes.

Press e on a selected node to stream its kernel ring buffer (dmesg). New output arrives live as it is produced.

The view reuses the same stream controls as service logs:

Key Result
/ Filter the visible lines.
s Pause or resume following.
w Toggle line wrapping.
C Clear the buffered lines.
r Reconnect the stream.

Dmesg output is bounded in memory: only the most recent 2000 lines are retained, so a busy node cannot grow the view without limit.

Press s on a selected node to list its network sockets: PROTO, STATE, LOCAL, REMOTE, and PROCESS. The list covers TCP, TCP6, UDP, and UDP6 sockets in the host network namespace in every state (listening and connected), matching what ss -tunap shows.

Press / to filter across protocol, state, local address, remote address, and process name. There is no detail page; the selected row carries all the surfaced fields.

Press m on a selected node to list its filesystem mounts: FILESYSTEM, SIZE, USED, AVAIL, USE%, and MOUNTED. USED is SIZE - AVAIL, and USE% is the used fraction of the mounted filesystem (reported as 0% when the size is unknown rather than dividing by zero).

Press / to filter across filesystem and mount point. There is no detail page; the selected row carries all the surfaced fields.

Press f on a selected node to show a curated subset of its /proc/meminfo as METRIC and VALUE rows: total, used (with the derived percentage of total), available, free, buffers, cached, swap total, swap free, dirty, and slab. Byte values are rendered with binary unit suffixes.

Press / to filter across the metric label and value. There is no detail page.

All four views are read-only. They never require --enable-writes, and enabling writes does not add any mutation to them.