Skip to main content
Expanse treats a Nomad cluster as a nomad compute. Install the daemon on a Nomad client node with access to the Nomad HTTP API, and Expanse captures allocations placed on the cluster.

​
What gets captured

For each Nomad allocation, Expanse records:
  • Allocation, job, group, task, namespace, region, datacenter, and node context.
  • Requested CPU, memory, and device resources, including GPU vendor and model where available.
  • Allocation and task state, task events, runtime, exit status, and failure context.
  • Bounded stdout and stderr log tails where Nomad authorises access.
  • Live CPU and memory metrics where the client exposes them.
  • Per-GPU utilisation and memory telemetry, and GPU-to-task attribution, captured automatically when nvidia-smi is present on the node. When it is missing, allocation capture continues without the per-allocation metric detail.
Those records appear in the Console and feed expanse analyse, expanse diagnose, and the intelligence layer.

​
Register Nomad

Register a compute and choose nomad when prompted:
The CLI prints a single-use install token and the daemon install command. Run the install command on a Nomad client node that can reach the Nomad HTTP API; the installer defaults the Nomad address to the local agent. Set EXPANSE_NOMAD_ADDR and EXPANSE_NOMAD_TOKEN if your agent listens elsewhere or has ACLs enabled.

​
Verify capture

Submit any Nomad job after the daemon starts. Within a minute of the allocation entering the scheduler, the nomad compute and the allocation appear in console.expanse.sh.

​
Next steps

Computes

How Nomad maps to the Expanse compute model.

Telemetry

What Expanse captures before, during, and after each allocation.