At this point you have learned how to run, inspect, and modify a job using the
nomad command-line tool; now you'll quickly explore the Nomad web interface.
If you arrive to this tutorial out of sequence, either complete the previous steps in this collection, or run
$ nomad agent -dev -bind 0.0.0.0 -log-level=INFO
»Open Nomad's web interface
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 /ui namespace.
With your Nomad dev agent running, visit http://localhost:4646 to open the Nomad UI. You should start at the jobs page. You should also see the example job from the previous tutorial.
»Troubleshooting
If you're using Vagrant and can't connect to the Nomad web interface, here are some possible causes.
»The Nomad dev agent was not started with the -bind value set to 0.0.0.0
Stop and restart the Nomad dev agent with the bind flag set to the proper value.
»There was a port collision when mapping 4646 back to the host
Vagrant chooses a new port to map to 4646 in the VM. Your vagrant up
output should contain the new port mapping:
==> default: Fixed port collision for 4646 => 4646. Now on port 2200.
Given this message, you would connect to http://localhost:2200 instead.
»Inspect a job
When you open the Nomad web interface, you begin at the Job list page. Select the example job from the list to view the job details.
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
to the nomad job status command.
»View cluster information
The Nomad web interface provides a way to view your Nomad cluster itself: servers, clients, and cluster topology.
»View servers
The Servers Page provides a sortable, filterable view of the Nomad server agents. You can drill down into an individual server's details from this list page.
»View clients
The Clients Page provides a sortable, filterable view of the Nomad client agents. You can drill down into an individual client's details from this list page.
»Cluster topology
The Nomad web interface's topology viewer provides an alternative view of the cluster and the running workload. In more complex environments, this view can help you understand where and how your workload is running, what jobs are running next to yours, and a high-level view of your used and open cluster capacity.
»Monitoring
The Nomad web interface also displays the Nomad application
logs at a user selectable log level. This parallels the nomad monitor
command in the command-line interface. You can access it from the individual
node's detail page. This works for both servers and clients.
»Next steps
In this tutorial, you explored Nomad's web interface, which offers a friendly and visual alternative experience to the command-line tool. This is a great opportunity to do more creative exploration around how the command-line interface and web interface might serve the needs of you and your users.
In the next tutorial, you will clean up your testing environment and consider what to focus on next on your Nomad journey.