This daemon is currently not monitored by Stork. The daemon has not been active since being added to the Stork server. This daemon appears in the list because its configuration was detected in the Kea Control Agent's configuration file.
If the daemon is operational (e.g. it allocates leases), make sure it has the
control-socket entry in its configuration file.
See the Kea ARM
See the Kea ARM
See the Kea ARM
for details.
The server tag is an arbitrary string assigned by the Kea administrator. If it is unassigned or empty, the effective server tag is all.
The same server tag can be assigned to one or multiple Kea servers. Configuration elements associated with a shared server tag are applied to all servers that use this tag.
Configuration elements associated with the all server tag apply to all servers, including servers that also have an explicit server tag.
If a server tag is all, only configuration elements with the all server tag apply to that server.
| {{ file.filetype }}: | {{ filenameFromFile(file) }} |
The Stork server reviews the monitored servers' configurations, flags potential configuration issues, and suggests changes to these configurations to improve Stork's monitoring capabilities. The review is performed using different checkers built into the Stork server. Each checker is responsible for examining a different part or aspect of the configuration. Each checker has a unique name, which is shown in the blue badge before the text of each issue in the list below.
Each checker can be disabled if its review report is not desired in a particular deployment.
By default, only reports that discover an issue are visible. Use the toggle button to display reports from all executed checkers for a given daemon.