Job details, logs and metrics
Opening it
Section titled “Opening it”Expand the job row, then select the service inside it. The detail panel opens on the service, not on the job.
Clicking the job row only expands it. With one service that is one extra click; it is worth knowing why, because nothing appears to happen otherwise.
Overview
Section titled “Overview”Started by, queue, node (with its id), start and end time, duration, and the resources the service actually got.
That last one is the useful part. If you left CPU and memory on automatic, this is where you find out what the scheduler gave you.
The ports this service declared, and whether each is open.
Empty on a job that declared none: “No ports configured. Add ports when creating a job to enable proxy access.” Ports cannot be added to a job after it is created, only opened and closed. See Ports and proxies.
Metrics
Section titled “Metrics”Usage over time for GPU, CPU and memory, each toggled on separately.
- The GPU chart appears only if the job asked for at least one GPU.
- Before the container starts there is nothing to draw, and the panel says so rather than showing an empty chart.
This is the view that answers “am I actually using the GPU I am paying for” - a job holding a GPU at 2% utilisation is a job that should have asked for fewer.
Configuration
Section titled “Configuration”The container image and the job type. What was asked for, as opposed to what was given.
Actions on a running service
Section titled “Actions on a running service”The panel header offers, while the service is running:
| Action | Does |
|---|---|
| Terminal | Opens a shell in the container. See Terminal and SSH |
| Show logs | The job’s log output |
| Extend | Adds time to this service |
| Clone job | Reopens the submission form with every setting from this job |
Restart appears on a running or failed job and starts its services again - either all of them, or just the selected one.
Editing
Section titled “Editing”A booked, queued, running or failed service can be edited in place: job name, image, command and ports. Save is refused while the image is empty, and anything you did not touch - registry, mounts - is kept as it was.
Finished and cancelled jobs offer no edit control, because the backend refuses the change. Clone them instead.