At this point you have a fully functioning cluster with a job running in it. You
have learned how to inspect a job using
nomad status, next you'll learn how to
inspect a job in the web client.
»Opening the Web UI
As long as Nomad is running, the Nomad UI is also running. It is hosted at the
same address and port as the Nomad HTTP API under the
With Nomad running, visit http://localhost:4646 to open the Nomad UI.
If you’re using vagrant and can’t connect, it’s possible that Vagrant was unable
to properly map the port from your host to the VM. Your
vagrant up output will
contain the new port mapping:
==> default: Fixed port collision for 4646 => 4646. Now on port 2200.
In the case above you would connect to http://localhost:2200 instead.
»Inspecting a Job
You should be automatically redirected to
/ui/jobs upon visiting the UI in
your browser. This pages lists all jobs known to Nomad, regardless of status.
example job to inspect it.
The job detail page shows pertinent information about the job, including overall
status as well as allocation statuses broken down by task group. It is similar
nomad status CLI command.
Note: You may see a different number of allocations on your node next to
Allocation Status depending on how many times you have stopped and
Click on the
cache task group to drill into the task group detail page. This
page lists each allocation for the task group.
Click on the allocation in the allocations table. This page lists all tasks for
an allocation as well as the recent events for each task. It is similar to the
nomad alloc status command.
The Nomad UI offers a friendly and visual alternative experience to the CLI.