Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.expanse.sh/llms.txt

Use this file to discover all available pages before exploring further.

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. GPU detail is opt-in and requires nvidia-smi on the node; when enabled but unavailable, the watcher is disabled and the daemon reports the gap on heartbeat.
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: 
expanse compute register
The CLI prints the daemon install command and Nomad configuration. Run the install command on a Nomad client node that can reach the Nomad HTTP API.

​
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.