Diagnostics — processes#

The Processes tab lists the processes running on the router. It refreshes every 10 seconds.

The four tiles#

Tile	Value
Processes	All the processes listed.
Kernel threads	Processes whose command is in square brackets, such as `[kworker/0:1]`. The second line reads Shown in [brackets].
User processes	All the processes except kernel threads.
Defunct	Processes that have finished but have not been cleared by the process that started them (state `Z`). Amber when there are any.

A few defunct processes that clear by themselves are normal. A count that keeps growing means a process is not clearing the ones it started.

Column	What it shows
PID	The process ID.
State	The process state. Green when it starts with `R` (running), red when it starts with `Z` (defunct).
CPU time	The processor time the process has used since it started.
Terminal	The terminal it is attached to; `?` for none.
Command	The full command line.

Every column sorts. The filter, Filter by command…, matches any column. The list scrolls within the panel.

Question	How
Is the Wheelhouse agent running?	Filter for `wheelhouse-agent`.
Is an app's container running?	Filter for `conmon`. An app's own page shows its state: Apps — detail.
Is the intrusion detection engine running?	Filter for `suricata`.
Which process has used the most processor time?	Sort by CPU time. It is the total since the process started, not its current use.

No current processor or memory use per process. The columns are the ones above.
No stopping or restarting. Nothing on this tab acts on a process.
No history. Each refresh replaces the list.
No process tree. Processes are a flat list.

For the router's load and memory, see the Overview. For what a service is doing, see Logs.

GET /api/processes (any role) returns the list, one object per process with its PID, terminal, state, processor time and command.