This page displays a list of all machines that have been configured in Stork. It allows machines to be added and removed.
The Unauthorized and Authorized buttons toggle between the machines that have been
registered using the agent token-based registration method, and those that have been authorized in
Stork. To authorize a machine on the Unauthorized list, either select the checkbox to the left
of the machine name and press the Authorize selected button, or click the blue button in the
Action column and select Authorize.
/var/lib/stork-agent/tokens/agent-token.txt
file. If they match, click on the
Action menu button on the right and then Authorize, or select the machine with the
checkbox on the left and click the Authorize selected button.
This page displays details about {{ !!machineTab?.authorized === false ? 'un' : '' }}authorized machine {{ machineTab?.hostname || machineTab?.address }}.
You can retrieve the latest machine's data from the Stork server by clicking Get Latest State button. It is possible to download data archive for machine's troubleshooting purposes by clicking Dump Troubleshooting Data button.
The Stork server will use the new address and/or port to communicate with this machine. Please ensure that the agent running on the machine is using this new address and/or port to avoid communication problems.
Copy these commands and paste them into a terminal on the machine where the Stork agent is being installed.
For more details, see
the Stork agent installation instructions .
During agent installation, you will be prompted for a server token.
The server token value is
Providing the token will cause the new machine to be automatically added to the Stork server and authorized.
If Enter is pressed with no token value provided, this new machine will wait for authorization. To see all unauthorized machines, select the Unauthorized button at the top right.
Address | {{ machineTab?.address }}:{{ machineTab?.agentPort }} |
Hostname | {{ machineTab?.hostname }} |
Agent Version |
{{ machineTab?.agentVersion }}
|
CPUs | {{ machineTab?.cpus }} |
CPUs Load
These three numbers are CPU load averages for the last 1 minute, 5 minutes, and 15 minutes. This is the usual syntax used by the top command. High load averages imply that a system is overloaded. A value of 1.00 means one CPU core is fully utilized. For example, if your system has load of 1.22 and you have only one CPU core, the system is overloaded. However, if the load is 1.22 with four cores, your system is working at slightly over 30% of its capacity. |
{{ machineTab?.cpusLoad }} |
Memory | {{ machineTab?.memory || '?' }} GiB |
Used Memory | {{ machineTab?.usedMemory }} % |
Uptime | {{ machineTab?.uptime || '?' }} days |
OS | {{ machineTab?.os }} |
Platform Family | {{ machineTab?.platformFamily }} |
Platform | {{ machineTab?.platform }} |
Platform Version | {{ machineTab?.platformVersion }} |
Kernel Version | {{ machineTab?.kernelVersion }} |
Kernel Arch | {{ machineTab?.kernelArch }} |
Virtualization Role | {{ machineTab?.virtualizationRole }} |
Virtualization System | {{ machineTab?.virtualizationSystem }} |
Host ID | {{ machineTab?.hostID }} |
Last Visited | {{ machineTab?.lastVisitedAt | localtime | placeholder: 'never' }} |