Infrastructure
Processes
Top processes by CPU and memory.
The story
These pages use illustrative scenarios to walk through real workbench panels. Sidebar labels, Bridge paths, and connection schemes match the app; characters and timelines are examples for learning.
CPU pegged — Processes sorts by usage, maps PID to port 8080, names the rogue worker.
Kill or restart from informed place, not kill -9 roulette.
Bridge path: /server/processes
Step 1
Top by CPU and memory
node worker 190% CPU — matches incident start time.
PID copied to terminal command.
Top processes by CPU and memory. /server/processes.
Step 2
PID to port
PID listens on 8080 — matches load balancer target.
Restart service not random kill.
Map to Ports & links.
Step 3
Watch during deploy
Deploy rolling — Processes confirms old PIDs gone.
Deploy verified.
Refresh during Operations work.
This panel appears in the Nexoxa Bridge left sidebar after you connect with the matching connection URL. See the connection docs above for
postgresql://, ssh://, sftp://, s3://, or smtp:// examples.Related connections