To add or remove machines, go to the Machines page
.

Using the settings in the Intervals section, you can configure the intervals at which the Stork server fetches various types of information from the monitored machines and applications. Each configured value designates the time period between the completion of the previous attempt to fetch certain information from the machines, and the beginning of the next attempt.

For example, if the Kea Hosts Puller Interval is set to 10 seconds and it takes five seconds to pull the hosts information, the time period between the start of two consecutive attempts to pull the hosts information will be 15 seconds. The pull time varies between deployments and depends on the amount of information pulled, network congestion, and other factors. The setting specified here guarantees that there is a constant idle time between any two attempts.

New machines begin registration in the Stork server using a dedicated REST API endpoint, and the same endpoint is used for re-registering already-connected machines when they are restarted. Since new machines are not registered often, it is practical to disable this option to prevent malicious registration attempts of fake machines; an administrator can re-enable it at any time when new registrations are expected. Disabling this option does not affect the ability to re-register existing machines.
Stork can automatically check for software updates available for Kea, BIND 9, and Stork itself. To do that, the Stork server downloads a JSON file with the latest software-release metadata. This feature can be disabled using this setting. When disabled, all feedback displayed regarding software versions detected by Stork is generated based on offline built-in information stored as a JSON file.
{{ setting.help }}
It is required.
It must not be negative.
{{ setting.help }}
{{ setting.help }}
There are issues with the form values.
Fetching current settings from the server failed. Click the button to retry.