This page displays a list of all machines that have been configured in Stork. It allows adding new machines as well as removing them.

If Show Unauthorized is toggled on, the list will show unauthorized machines. They were registered using the agent token-based registration method. To authorize a machine, click action menu button and then Authorize.

Stork server will be using 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.

Address:
Port:

Copy these commands and paste them into a terminal on a machine where Stork Agent is going to be installed.
For more details check the Stork Agent Installation instructions.

During agent installation you will be prompted for a server token.

Server token value is

Providing the token will cause the new machine to be automatically added and authorized in the Stork Server.

If no token value is provided (just Enter is hit) then this new machine will be waiting for authorization. To see unauthorized machines select the Unauthorized button at the top right.

{{ item.label }}
Filter machines:

Machines in the table below can be filtered by entering a text in the search box; the table shows all machines matching the filter text. Currently supported fields for such filtering are:

  • Address
  • Agent Version
  • Hostname
  • OS
  • Platform
  • Platform Family
  • Platform Version
  • Kernel Version
  • Kernel Arch
  • Virtualization System
  • Virtualization Role
  • Host ID

The search is performed while typing or on pressing Enter. The minimum number of search characters is 2.

No {{ showUnauthorized ? 'unauthorized' : 'authorized' }} machines found.
Information about adding new machines to Stork server is available after clicking on the How to Install Agent to New Machine button at the top.
There {{ unauthorizedMachinesCount === 1 ? 'is' : 'are' }} {{ unauthorizedMachinesCount }} unauthorized machine{{ unauthorizedMachinesCount > 1 ? 's' : '' }}. Check {{ unauthorizedMachinesCount === 1 ? 'it' : 'them' }} by selecting Unauthorized button above.
There are no machines waiting for the authorization. You can now select the Authorized button above to see all authorized machines.
Hostname Location

Specifies where the server can reach the agent as a hostname:tcp-port pair (e.g. localhost:8888).

Agent Version Daemons CPUs CPU Load

These three numbers are CPU load averages for last 1 minute, 5 minutes and 15 minutes. This is the usual syntax used by 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 1 CPU core, the system is overloaded. However, if there are 4 cores, you system is working at a bit over 30% of its capacity.

Total Memory [GB] Memory Usage [%] Uptime Last Refreshed

When the machine status was last retrieved. You can refresh it by clicking Refresh in the Action menu.

Error Action Hostname Location

Specifies a host name and the TCP port where the server can reach the agent, e.g. localhost:8888).

Agent Token

This is a token generated by an agent during its first start up. Verify if value visible here is the same as agent token present in its logs or in /var/lib/stork-agent/tokens/agent-token.txt.

Action
{{ m.hostname || m.address }} {{ m.address }}:{{ m.agentPort }} {{ m.agentVersion }}
{{ m.cpus }} {{ m.cpusLoad }} {{ m.memory }} {{ m.uptime || '?' }} days {{ m.lastVisitedAt | localtime | placeholder: 'never' }} {{ m.hostname || m.address }} {{ m.address }}:{{ m.agentPort }} {{ m.agentToken }}
Total: {{ state.totalRecords > 0 ? state.totalRecords : '0' }} {{ state.totalRecords === 1 ? 'machine' : 'machines' }}
{{ machineTab.machine.address }}:{{ machineTab.machine.agentPort }}

System Information

Address {{ machineTab.machine.address }}:{{ machineTab.machine.agentPort }}
Hostname {{ machineTab.machine.hostname }}
Agent Version {{ machineTab.machine.agentVersion }}
CPUs {{ machineTab.machine.cpus }}
CPUs Load

These three numbers are CPU load averages for last 1 minute, 5 minutes and 15 minutes. This is the usual syntax used by 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 1 CPU core, the system is overloaded. However, if there are 4 cores, you system is working at a bit over 30% of its capacity.

{{ machineTab.machine.cpusLoad }}
Memory {{ machineTab.machine.memory || '?' }} GiB
Used Memory {{ machineTab.machine.usedMemory }} %
Uptime {{ machineTab.machine.uptime || '?' }} days
OS {{ machineTab.machine.os }}
Platform Family {{ machineTab.machine.platformFamily }}
Platform {{ machineTab.machine.platform }}
Platform Version {{ machineTab.machine.platformVersion }}
Kernel Version {{ machineTab.machine.kernelVersion }}
Kernel Arch {{ machineTab.machine.kernelArch }}
Virtualization Role {{ machineTab.machine.virtualizationRole }}
Virtualization System {{ machineTab.machine.virtualizationSystem }}
Use HTTP credentials

Indicates if the Stork Agent includes the HTTP credentials (i.e., Basic Auth user and password) in the requests sent to the Kea Control Agent.

The credentials are included only in the requests to the hosts specified in the configuration file. Other hosts don't receive any authorization data.

{{ !!machineTab.machine.agentUsesHttpCredentials }}
Host ID {{ machineTab.machine.hostID }}
Last Visited {{ machineTab.machine.lastVisitedAt | localtime | placeholder: 'never' }}

Applications

Kea App ({{ app.name }})

BIND 9 App

Version {{ app.version }}

Events