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

First, install Stork Agent on the machine with Kea or BIND 9. This is described in the Stork Agent instructions.

Machine is located by address and port where 'address' is the IP address or FQDN of machine, and port is the Stork Agent listening port. Port can be omitted; default value is 8080.

Address:
Port:

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:
{{ 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 machines found.

Machines can be added by clicking the Add New Machine button at the top.
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
{{ m.hostname || m.address }} {{ m.address }}:{{ m.agentPort }} {{ m.agentVersion }}
{{ m.cpus }} {{ m.cpusLoad }} {{ m.memory }} {{ m.uptime || '?' }} days {{ m.lastVisitedAt | localtime }}
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 }}
Hostame {{ 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 }}
Host ID {{ machineTab.machine.hostID }}
Last Visited {{ machineTab.machine.lastVisitedAt | localtime }}

Applications

Kea App

BIND 9 App

Version {{ app.version }}

Events