Getting Node Details

From the Nodes page (see Listing Nodes), click any row to open a Node details dialog showing:

• Node Information: ID, hostname, CPU, and memory.
• Health: scheduling status, health state, reliability score and when the node last reported. A node that has not been scored yet shows Not yet scored rather than a zero.
• Score breakdown: what each active condition deducted from the score, and any deduction from job failures attributed to the node. Shown only when points have been deducted.
• Conditions: active health findings with their severity, detail, and when each was first seen. Shown only when the node has any.
• Attributed job failures: how many job failures were charged to this node, broken down by fault class. Shown only when there are any.
• Resource Summary: total, allocated, and available cores and memory.
• Device Summary: per-device counts (total, requested, and available) when consumable devices are present on the node.
• Running Jobs: each running job’s ID, name, workflow ID, requested cores and memory, requested devices, and start time. Click a Job ID to jump to that job within its workflow.

Get detailed information about a specific node by providing its node ID:

$ fuzzball node show <node-id>

Example:

$ fuzzball node show 172.21.0.6/7333
ID:        172.21.0.6/7333
Hostname:  substrate-localnode-1
CPU:       cpu/arm64
Substrate: v2.6.0
Cluster:   local-dev
Status:    Ready
Health:    Healthy (last reported 2026-08-05T14:05:00Z)
Score:     100/100 (penalties: default)
Resources:
  Cores:     20 total (1 allocated, 19 available)
  Memory:    127.9 GB total (1.0 GB allocated, 126.9 GB available)
  nvidia.com/gpu:  1 total (0 requested, 1 available)

JOB ID                               | JOB NAME        | REQUESTED CORES | REQUESTED MEMORY (GB) | REQUESTED DEVICES
fab5985c-3157-5e6c-b60b-f2fd8e17fefd   data-processing   2                 4.0                     nvidia.com/gpu:1
e3211b77-117a-54ce-a2d9-420b4c673416   Hidden Job        1                 1.0                     None

The output includes:

• ID: Node identifier
• Hostname: Network hostname
• CPU: CPU model name or architecture
• Substrate: The fuzzball-substrate version running on the node, as reported by substrate itself. Only shown when the node reports it (older substrate versions omit it).
• Cluster: Resolved name of the Fuzzball cluster this node belongs to, or the raw cluster_id if the name cannot be resolved. Only shown when cluster_id is present — most visible when connected to a Federate cluster where nodes span multiple underlying Orchestrate clusters.

• Status: Scheduling status – Ready, Not Ready, Offline or Cordoned
• Health: Health state and when the node last reported. A node that has not reported yet shows Unknown with no timestamp.
• Score: Reliability score out of 100, followed by the penalty configuration that produced it. When points have been deducted, each contributing condition is listed beneath it. A node that has not been scored yet shows not yet scored rather than a zero.
• Conditions: Active health findings, with severity, message, when each was first seen, and how many times it has been observed. Omitted when the node has none.
• Attributed job failures: Job failures charged to this node, broken down by fault class. Omitted when there are none.

For the meaning of each condition and how scoring is configured, see Node Health Monitoring.

• Total: Capacity of the node
• Allocated: Currently in use by running jobs
• Available: Free capacity for new jobs

Consumable resources are tracked per device type:

• Total Count: Number of devices installed on the node
• Requested Count: Devices currently requested by jobs
• Available Count: Devices remaining that are not requested by jobs

For each job that is currently running on the node:

• JOB ID: Unique identifier for the job
• JOB NAME: Job name from the workflow definition
• REQUESTED CORES: CPU cores requested by the job
• REQUESTED MEMORY (GB): Memory requested by the job
• REQUESTED DEVICES: Consumable devices requested by the job

Jobs shown are workflow stages currently executing on this node. If you don’t have permission to view the corresponding workflow, the job will appear as “Hidden Job” with only the job ID visible.

By default the command prints the human-readable summary shown above. For programmatic access or scripting, request structured output with -o json or -o yaml:

$ fuzzball node show <node-id> -o json

The structured output includes additional low-level fields not shown in the default view, suitable for parsing with tools like jq or yq.