Skip to main content

Running Processes

The Processes tab lists what's actually running on the device — process name, PID, and CPU/memory usage — so you can find resource hogs and decide what to restart or investigate.

Using it​

  • Sort by CPU to find what's pinning the processor.
  • Sort by Memory to spot leaks or bloated services.
  • Cross‑reference a spike here with the Metrics timeline to see when it started.

Acting on a process​

The process list is a read view. To act on what you find, use the Terminal or NL Ops — for example, tell NL Ops "kill process <name>" or restart a service. That way the action is logged in Ops Replay.

tip

High CPU on a single process right after a deploy usually means a stuck worker — restart it and watch Metrics settle.