{{ appTab.app.name }}
{{ daemon.niceName }}

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.

Overview

Version
{{ daemon.version }}
Version Ext
Uptime
{{ showDuration(daemon.uptime) }}
Last Reloaded At
{{ daemon.reloadedAt | localtime | placeholder: 'never' }}
  1. {{ basename(hook) }}
No hooks

Data Storage

{{ file.filetype }}: {{ filenameFromFile(file) }}
{{ databaseNameFromType(backend.backendType) }} ({{ backend.database }}@{{ backend.host }}) with:
  • {{ dataType }}

Loggers

Logger Severity Output Location {{ logTarget.name }} {{ logTarget.severity }} {{ logTarget.output }} {{ logTarget.output }} No loggers found

Configuration Review Reports

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.

Events