This page covers where to read an instance's output, how to get your own programs' output into it, what the metrics tell you, and where to see what happened to an instance.
Logs show what the instance's main process writes to standard output and error: its start command, or the image's own command when there's none. Open the instance and select the Logs tab, or use the CLI:
featherless-cloud instance logs my-instance
featherless-cloud instance logs my-instance --follow
featherless-cloud instance logs my-instance --head
Each start or restart begins a new run, and you can pick the run to view. For each run, the first and last 50 MB of output are kept; longer output loses its middle part. Output is kept for 30 days after its last line.
Programs you start in the terminal or over SSH don't write to the logs; their output stays in that terminal. To send it to the logs as well, write to the main process's output:
python train.py 2>&1 | tee -a /proc/1/fd/1
echo "checkpoint saved" > /proc/1/fd/1
To have a program's output in the logs from the start, make it the instance's start command.
The Metrics tab charts CPU, memory and network use, and on GPU instances each GPU's utilization and memory, over the last hour, 24 hours, 7 days or 30 days. Use it to spot:
DataLoader workers.For a live view inside the instance, the PyTorch (ROCm) template includes nvtop and amd-smi.
The Activity tab lists every event in the instance's life, with the time and who caused it: compute being assigned, starts, stops, failures and automatic stops with their reason, and setting changes such as public ports. From the CLI:
featherless-cloud instance history my-instance