3. Using Stork
This section describes how to use the features available in Stork. To
connect to Stork, use a web browser and connect to port 8080 on the Stork server machine. If
stork-server is running on a localhost, it can be reached by navigating to
3.1. Managing Users
A default administrator account is created when Stork is initially installed. It can be used to
sign in to the system via the web UI, with the username
admin and password
To see a list of existing users, click on the
Configuration menu and
Users. There will be at least one user,
To add a new user, click
Create User Account. A new tab opens to
specify the new account parameters. Some fields have specific
usernamecan consist of only letters, numbers, and an underscore (_).
lastnamefields are mandatory.
passwordmust only contain letters, digits, @, ., !, +, or -, and must be at least eight characters long.
Currently, each user is associated with one of the two predefined groups
(roles), which are
admin; one of these must be selected
when a user account is created. Both types of users can view Stork
status screens, edit interval and reporting configuration settings, and
add/remove machines for monitoring.
super-admin users can also
create and manage user accounts.
Once the new user account information has been specified and all
requirements are met, the
Save button becomes active and the new
account can be enabled.
3.2. Changing a User Password
An initial password is assigned by the administrator when a user
account is created. Each user should change their password when first
logging into the system. To change the password, click on the
Profile menu and choose
Settings to display the user profile
information. Click on
Change password in the menu bar on the left
and specify the current password in the first input box. The new
password must be entered and confirmed in the second and third input
boxes, and must meet the password requirements specified in the
previous section. When all entered data is valid, the
is activated to change the password.
3.3. Configuration Settings
It is possible to control some of the Stork configuration settings from
the web interface. Click on the
Configuration menu and choose
There are two classes of settings available:
Grafana & Prometheus.
Intervals settings specify the configuration of “pullers.” A puller is a
mechanism in Stork which triggers a specific action at the
specified interval. Each puller has its own specific action and
interval. The puller interval is specified in seconds and designates
a time period between the completion of the previously invoked action
and the beginning of the next invocation of this action. 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
starts of the two consecutive attempts to pull the hosts information is
The pull time varies between deployments and depends on the amount of information pulled, network congestion, and other factors. The interval setting guarantees that there is a constant idle time between any consecutive attempts.
Grafana & Prometheus settings currently allow the URLs
of the Prometheus and Grafana instances used with Stork to be specified.
3.4. Connecting and Monitoring Machines
3.4.1. Monitoring a Machine
Monitoring of registered machines is accomplished via the
Machines. A list of currently registered machines is
displayed, with multiple pages available if needed.
A filtering mechanism that acts as an omnibox is available. Via a typed string, Stork can search for an address, agent version, hostname, OS, platform, OS version, kernel version, kernel architecture, virtualization system, or host ID field.
The state of a machine can be inspected by clicking its hostname; a
new tab opens with the machine’s details. Multiple tabs can be open at
the same time, and clicking
Refresh updates the available information.
The machine state can also be refreshed via the
Action menu. On the
Machines list, each machine has its own menu; click on the
triple-lines button at the right side and choose the
3.4.2. Disconnecting From a Machine
To stop monitoring a machine, go to the
Machines list, find the
machine to stop monitoring, click on the triple-lines button at the
right side, and choose
Delete. This terminates the connection
between the Stork server and the agent running on the machine, and the
server will no longer monitor that machine; however, the
will continue running. Complete shutdown of a
stork-agent process must be done manually, e.g. by connecting to the machine
using ssh and stopping the agent there. For example, when the Stork Agent
has been installed from packages, run:
$ sudo systemctl stop isc-stork-agent
$ sudo killall -9 stork-agent
3.4.3. Dumping Diagnostic Information Into a File
It is sometimes difficult or impossible to diagnose issues without seeing the actual logs, database contents, and configuration files. Gathering such information can be challenging for a user because it requires looking into many places like databases, remote machine logs, etc.
Stork makes it convenient for users to gather diagnostic information from the
selected machines with a single click. Navigate to the
Machines page (i.e.,
the page where all monitored machines are listed), click on the
for the selected machine, and choose the
Dump Troubleshooting Data option. Alternatively,
navigate to the selected machine’s page and click on the
Dump Troubleshooting Data
button at the bottom of the page. In both cases, the Stork server will
automatically gather useful diagnostics information and offer it for download as a
tar.gz file. The downloaded package contains configurations, log tails,
stork-server settings, warning and error-level events, etc.
Stork sanitizes passwords and other sensitive information when it creates the package.
The tarball can be easily sent via email or attached to a bug report.
3.5. Monitoring Applications
3.5.1. Application Status
Kea DHCP applications discovered on connected machines are
listed via the top-level menu bar, under
Services. The list view includes the
application version, application status, and some machine details. The
Action button is also available, to refresh the information about
The application status displays a list of daemons belonging to the application. Several daemons may be presented in the application status columns; typically, they include: DHCPv4, DHCPv6, DDNS, and Kea Control Agent (CA).
rndc to retrieve the application’s status. It looks for
controls statement in the configuration file, and uses the
first listed control point for monitoring the application.
Furthermore, the Stork agent can be used as a Prometheus exporter
named is built with
it gathers statistics via the JSON statistics API. The
named.conf file must have
the exporter queries the first listed channel. Stork is able to export the
most metrics if
zone-statistics is set to
full in the
For Kea, the listed daemons are those that Stork finds in the Control Agent (CA) configuration file. A warning sign is displayed for any daemons from the CA configuration file that are not running. When the Kea installation is simply using the default CA configuration file, which includes configuration of daemons that are never intended to be launched, it is recommended to remove (or comment out) those configurations to eliminate unwanted warnings from Stork about inactive daemons.
3.5.2. Friendly App Names
Every app connected to Stork is assigned a default name. For example,
if a Kea app runs on the machine
abc.example.org, this app’s default name
email@example.com. Similarly, if a BIND 9 app runs on the machine
with the address
192.0.2.3, the resulting app name is
If multiple apps of a given type run on the same machine, a postfix with a
unique identifier is appended to the duplicated names, e.g.
The default app names are unique so that the user can distinguish them in the dashboard, apps list, events panel, and other views. However, the default names may become lengthy when machines names consist of fully qualified domain names. When machines’ IP addresses are used instead of FQDNs, the app names are less meaningful for someone not familiar with addressing in the managed network. In these cases, users may prefer replacing the default app names with more descriptive ones.
Suppose there are two DHCP servers in the network, one on the first floor of a building
and one on the second floor. A user may assign the names
Floor 1 DHCP
Floor 2 DHCP to the respective DHCP servers in this case.
The new names need not have the same pattern as the default names and may
contain whitespace. The @ character is not required, but if it is present,
the part of the name following this character (and before an optional %
character) must be an address or name of the machine monitored in Stork.
The following names:
are invalid unless
floor1 is a monitored machine’s name. The special
notation using two consecutive @ characters can be used to suppress this
dhcp-server@@floor1 is a valid name even if
not a machine’s name. In this case,
floor1 can be a physical location
of the DHCP server in a building.
To modify an app’s name, navigate to the selected app’s view. For example,
Services from the top menu bar and then click
Select an app from the presented apps list. Locate and click the pencil
icon next to the app name in the app view. In the displayed dialog box,
type the new app name. If the specified name is valid, the
button is enabled. Click this button to submit the new name. The
button is disabled if the name is invalid. In this case, a hint is displayed
to explain the issues with the new name.
3.5.3. IPv4 and IPv6 Subnets per Kea Application
One of the primary configuration aspects of any network is the layout of IP addressing. This is represented in Kea with IPv4 and IPv6 subnets. Each subnet represents addresses used on a physical link. Typically, certain parts of each subnet (“pools”) are delegated to the DHCP server to manage. Stork is able to display this information.
One way to inspect the subnets and pools within Kea is by looking at each Kea application to get an overview of what configurations a specific Kea application is serving. A list of configured subnets on that specific Kea application is displayed. The following picture shows a simple view of the Kea DHCPv6 server running with a single subnet, with three pools configured in it.
3.5.4. IPv4 and IPv6 Subnets in the Whole Network
It is convenient to see the complete overview of all subnets
configured in the network that are being monitored by Stork. Once at least one
machine with the Kea application running is added to Stork, click on
DHCP menu and choose
Subnets to see all available subnets. The
view shows all IPv4 and IPv6 subnets, with the address pools and links
to the applications that are providing them. An example view of all
subnets in the network is presented in the figure below.
Stork provides filtering capabilities; it is possible to choose whether to see IPv4 only, IPv6 only, or both. There is also an omnisearch box available where users can type a search string. For strings of four characters or more, the filtering takes place automatically, while shorter strings require the user to hit Enter. For example, in the above example it is possible to show only the first (192.0.2.0/24) subnet by searching for the 0.2 string. One can also search for specific pools, and easily filter the subnet with a specific pool, by searching for part of the pool range, e.g. 3.200.
Stork displays pool utilization for each subnet, with the absolute number of addresses allocated and usage percentage. There are two thresholds: 80% (warning; the pool utilization bar turns orange) and 90% (critical; the pool utilization bar turns red).
3.5.5. IPv4 and IPv6 Networks
Kea uses the concept of a shared network, which is essentially a stack
of subnets deployed on the same physical link. Stork
retrieves information about shared networks and aggregates it across all
configured Kea servers. The
Shared Networks view allows the
inspection of networks and the subnets that belong in them. Pool
utilization is shown for each subnet.
3.5.6. Host Reservations
188.8.131.52. Listing Host Reservations
Kea DHCP servers can be configured to assign static resources or parameters to the DHCP clients communicating with the servers. Most commonly these resources are the IP addresses or delegated prefixes. However, Kea also allows assignment of hostnames, PXE boot parameters, client classes, DHCP options, and other parameters. The mechanism by which a given set of resources and/or parameters is associated with a given DHCP client is called “host reservations.”
A host reservation consists of one or more DHCP identifiers used to associate the reservation with a client, e.g. MAC address, DUID, or client identifier; and a collection of resources and/or parameters to be returned to the client if the client’s DHCP message is associated with the host reservation by one of the identifiers. Stork can detect existing host reservations specified both in the configuration files of the monitored Kea servers and in the host database backends accessed via the Kea Host Commands premium hook library. At present, Stork provides no means to update or delete host reservations.
All reservations detected by Stork can be listed by selecting the
menu option and then selecting
The first column in the presented view displays one or more DHCP identifiers
for each host in the format
hw-address is the identifier type. In this case, the identifier type is
the MAC address of the DHCP client for which the reservation has been specified.
Supported identifier types are described in the following sections of the Kea
Administrator Reference Manual (ARM):
Host Reservation in DHCPv4
and Host Reservation in DHCPv6.
If multiple identifiers are present for a reservation, the reservation is
assigned when at least one of the identifiers matches the received DHCP packet.
The second column,
IP Reservations, includes the static assignments of the
IP addresses and/or delegated prefixes to the clients. There may be one or
more IP reservations for each host.
Hostname column contains an optional hostname reservation, i.e., the
hostname assigned to the particular client by the DHCP servers via the
Hostname or Client FQDN option.
Global/Subnet column contains the prefixes of the subnets to which the reserved
IP addresses and prefixes belong. If the reservation is global, i.e., is valid
for all configured subnets of the given server, the word “global” is shown
instead of the subnet prefix.
App Name column includes one or more links to
Kea applications configured to assign each reservation to the
client. The number of applications is typically greater than one
when Kea servers operate in the High Availability setup. In this case,
each of the HA peers uses the same configuration and may allocate IP
addresses and delegated prefixes to the same set of clients, including
static assignments via host reservations. If HA peers are configured
correctly, the reservations they share will have two links in the
App Name column. Next to each link there is a label indicating
whether the host reservation for the given server has been specified
in its configuration file or a host database (via the Host Commands premium
Filter hosts input box is located above the
Hosts table. It
allows the hosts to be filtered by identifier types, identifier values, IP
reservations, and hostnames, and by globality, i.e.,
When filtering by DHCP identifier values, it is not necessary to use
colons between the pairs of hexadecimal digits. For example, the
hw-address=0a:1b:bd:43:5f:99 will be found
whether the filtering text is
184.108.40.206. Host Reservation Usage Status
Clicking on a selected host in the host reservations list opens a new tab
that shows host details. The tab also includes information about
reserved addresses and delegated prefixes usage. Stork needs to query Kea
servers to gather the lease information for each address and prefix in the
selected reservation. It may take several seconds or longer before this
information is available. The lease information can be refreshed using the
Leases button at the bottom of the tab.
The usage status is shown next to each IP address and delegated prefix. Possible statuses and their meanings are listed in the table below.
There are valid leases assigned to the client. The client
owns the reservation, or the reservation includes the
At least one of the leases assigned to the client owning the reservation is expired.
The address is declined on at least one of the Kea servers.
At least one of the leases for the given reservation is assigned to a client that does not own this reservation.
There are no leases for the given reservation.
View status details by expanding a selected address or delegated prefix row. Clicking on the selected address or delegated prefix navigates to the leases search page, where all leases associated with the address or prefix can be listed.
in conflict status is currently not supported for host
circuit-id identifiers. If there are
valid leases for such reservations, they are marked
in use regardless
of whether the conflict exists.
220.127.116.11. Sources of Host Reservations
There are two ways to configure Kea servers to use host reservations. First,
the host reservations can be specified within the Kea configuration files; see
Host Reservation in DHCPv4
for details. The other way is to use a host database backend, as described in
Storing Host Reservations in MySQL, PostgreSQL, or Cassandra.
The second solution requires the given Kea server to be configured to use the
host_cmds premium hook library. This library implements control commands used
to store and fetch the host reservations from the host database to which the Kea
server is connected. If the
host_cmds hook library is not loaded, Stork
only presents the reservations specified within the Kea configuration files.
Stork periodically fetches the reservations from the host database backends and updates them in the local database. The default interval at which Stork refreshes host reservation information is set to 60 seconds. This means that an update in the host reservation database is not visible in Stork until up to 60 seconds after it was applied. This interval is configurable in the Stork interface.
The list of host reservations must be manually refreshed by reloading the browser page to see the most recent updates fetched from the Kea servers.
18.104.22.168. Creating Host Reservations
Above the list of the host reservations, there is the
New Host button
that opens a tab where a user can specify a new host reservation in one or
more Kea servers. These Kea servers must be configured to use the
hooks library, and only these servers are available for selection in
DHCP Servers dropdown.
A user has a choice between a subnet-level or global host reservation.
Selecting a subnet using the
Subnet dropdown is required for a
subnet-level reservation. If the desired subnet is not displayed in the
dropdown, it is possible that the selected DHCP servers do not include this
subnet in their configuration. Setting the
Global reservation option
disables subnet selection.
To associate the new host reservation with a DHCP client, the user can select
one of the identifier types supported by Kea. Available identifiers differ
depending on whether the user selected DHCPv4 or DHCPv6 servers. The identifier
can be specified using
text format. For example, the
is typically specified as a string of hexadecimal digits:
In that case, select
hex option. Some identifiers, e.g.
often specified using “printable characters”, e.g.
circuit-no-1. In that case,
text option. Please refer to
Host Reservations in DHCPv4
and Host Reservations in DHCPv6
for more details regarding allowed DHCP identifiers and their formats.
Further in the form, the user can specify the actual reservations. It is possible to specify at most one IPv4 address. In the case of the DHCPv6 servers, it is possible to specify multiple IPv6 addresses and delegated prefixes.
Hostname is currently the only supported non-IP reservation type. Submitting
the host reservation is possible after specifying at least one IP reservation or
Kea configuration with Stork is a new feature under development. Thus, it lacks many configuration capabilities, e.g., DHCP options, client classes, etc. Stay tuned for these capabilities in the subsequent Stork releases.
Submitted host reservations may appear in Stork’s host reservations list with some delay. Please allow some time for the reservations to propagate to the Kea DHCP servers and refresh the list.
3.5.7. Leases Search
Stork can search DHCP leases on monitored Kea servers, which is helpful for troubleshooting issues with a particular IP address or delegated prefix. It is also helpful in resolving lease allocation issues for certain DHCP clients. The search mechanism utilizes Kea control commands to find leases on the monitored servers. An operator must ensure that any Kea servers on which he intends to search the leases have the lease commands hook library loaded. Stork does not search leases on Kea instances without this library.
The leases search is available via the
DHCP -> Leases Search menu. Enter one
of the searched lease properties in the search box:
IPv4 address, e.g.
IPv6 address or delegated prefix without prefix length,
MAC address, e.g.
DHCPv4 Client Identifier, e.g.
DHCPv6 DUID, e.g.
All identifier types can also be specified using the notation with spaces, e.g. 01 02 03 04 05 06, or the notation with hexadecimal digits only, e.g. 010203040506.
To search all declined leases, type
state:declined. Be aware that this query may
return a large result if there are many declined leases, and thus the query
processing time may also increase.
Searching using partial text is currently unsupported. For example: searching by
partial IPv4 address
192.0.2 is not accepted by the search box. Partial MAC
01:02:03 is accepted but will return no results. Specify the complete
MAC address instead, e.g.
01:02:03:04:05:06. Searching leases in states other
declined is also unsupported. For example, the text
is not accepted by the search box.
The search utility automatically recognizes the specified lease type property and communicates with the Kea servers to find leases using appropriate commands. Each search attempt may result in several commands to multiple Kea servers; therefore, it may take several seconds or more before Stork displays the search results. If some Kea servers are unavailable or return an error, Stork shows leases found on the servers which returned success status, and displays a warning message containing the list of Kea servers that returned an error.
If the same lease is found on two or more Kea servers, the results list contains all that lease’s occurrences. For example, if there is a pair of servers cooperating via the High Availability hook library, the servers exchange the lease information, and each of them maintains a copy of the lease database. In that case, the lease search on these servers typically returns two occurrences of the same lease.
To display the detailed lease information, click the expand button (
>) in the
first column for the selected lease.
3.5.8. Kea High Availability Status
When viewing the details of the Kea application for which High
Availability (HA) is enabled (via the
libdhcp_ha.so hook library), the
High Availability live status is presented and periodically refreshed
for the DHCPv4 and/or DHCPv6 daemon configured as primary or
secondary/standby server. The status is not displayed for the server
configured as an HA backup. See the High Availability section in the
for details about the roles of the servers within the HA setup.
The following picture shows a typical High Availability status view displayed in the Stork UI.
The local server is the DHCP server (daemon) belonging to the
application for which the status is displayed; the remote server is
its active HA partner. The remote server belongs to a different
application running on a different machine; this machine may or
may not be monitored by Stork. The statuses of both the local and the
remote servers are fetched by sending the status-get
command to the Kea server whose details are displayed (the local
server). In the load-balancing and hot-standby modes, the local server
periodically checks the status of its partner by sending it the
ha-heartbeat command. Therefore, this information is not
always up-to-date; its age depends on the heartbeat command interval
(typically 10 seconds). The status of the remote server returned by Stork includes the
age of the data displayed.
The Stork status information contains the role, state, and scopes served by
each HA partner. In the usual HA case, both servers are in
load-balancing state, which means that both are serving DHCP
clients. If the remote server crashes, the
local server transitions to the
partner-down state, which will be
reflected in this view. If the local server crashes, this will
manifest itself as a communication problem between Stork and the
As of the Stork 0.8.0 release, the High Availability view also contains information about the heartbeat status between the two servers and information about failover progress.
The failover progress information is only presented when one of the
active servers has been unable to communicate with the partner via
the heartbeat exchange for a time exceeding the
threshold. If the server is configured to monitor the DHCP traffic
directed to the partner, to verify that the partner is not responding
to this traffic before transitioning to the
partner-down state, the
number of “unacked” clients (clients which failed
to get a lease), connecting clients (all clients currently trying
to get a lease from the partner), and analyzed
packets are displayed. The system administrator may use this information
to diagnose why the failover transition has not taken place or when
such a transition is likely to happen.
More about the High Availability status information provided by Kea can be found in the Kea ARM.
3.5.9. Viewing the Kea Log
Stork offers a simple log-viewing mechanism to diagnose issues with monitored applications.
This mechanism currently only supports viewing Kea log files; viewing BIND 9 logs is not yet supported. Monitoring other logging locations such as stdout, stderr, or syslog is also not supported.
Kea can be configured to log into multiple destinations. Different types
of log messages may be output into different log files: syslog, stdout,
or stderr. The list of log destinations used by the Kea application
is available on the
Kea App page. Click on the Kea app to view its logs.
Next, select the Kea daemon by clicking on one of the
tabs, e.g. the
DHCPv4 tab. Scroll down to the
This section contains a table with a list of configured loggers for the selected daemon. For each configured logger, the logger’s name, logging severity, and output location are presented. The possible output locations are: log file, stdout, stderr, or syslog. It is only possible to view the logs’ output to the log files. Therefore, for each log file there is a link which leads to the log viewer showing the selected file’s contents. The loggers which output to the stdout, stderr, and syslog are also listed, but links to the log viewer are not available for them.
Clicking on the selected log file navigates to its log viewer. By default, the viewer displays the tail of the log file, up to 4000 characters. Depending on the network latency and the size of the log file, it may take several seconds or more before the log contents are fetched and displayed.
The log viewer title bar comprises three buttons. The button with the refresh
icon triggers a log-data fetch without modifying the size of the presented
data. Clicking on the
+ button extends the size of the viewed log tail
by 4000 characters and refreshes the data in the log viewer. Conversely,
clicking on the
- button reduces the amount of presented data by
4000 characters. Each time any of these buttons is clicked, the viewer
discards the currently presented data and displays the latest part of the
log file tail.
Please keep in mind that extending the size of the viewed log tail may cause slowness of the log viewer and network congestion as the amount of data fetched from the monitored machine increases.
3.5.10. Viewing the Kea Configuration as a JSON Tree
Kea App view, select the appropriate tab for the daemon
configuration to be inspected, and then click on the
button. The displayed tree view comprises the selected daemon’s
configuration fetched using the Kea
config-get command returns the configuration currently in use
by the selected Kea server. It is a combination of the configuration
read from the configuration file and from the config backend, if Kea uses
the backend. Therefore, the configuration tree presented in Stork may
differ (sometimes significantly) from the configuration file contents.
The nodes with complex data types can be individually expanded and
collapsed. All nodes can also be expanded or collapsed by toggling
Expand button. When expanding nodes
with many sub-nodes, they may be paginated to avoid degrading browser
Refresh button to fetch and display the latest configuration.
Download to download the entire configuration into a text file.
Some of the configuration fields may contain sensitive data (e.g. passwords or tokens). The content of these fields is hidden, and a placeholder is shown. Configurations downloaded as JSON files by users other than super-admins contain null values in place of the sensitive data.
The main Stork page presents a dashboard. It contains a panel with information about DHCP and a panel with events observed or noticed by the Stork server.
3.6.1. DHCP Panel
The DHCP panel includes two sections: one for DHCPv4 and one for DHCPv6. Each section contains three kinds of information:
a list of up to five subnets with the highest pool utilization.
a list of up to five shared networks with the highest pool utilization
statistics about DHCP.
3.6.2. Events Panel
The Events panel presents the list of the most recent events captured by the Stork server. There are three event urgency levels: info, warning, and error. Events pertaining to the particular entities, e.g. machines or applications, provide a link to a web page containing information about the given object.
3.7. Events Page
The Events page presents a list of all events. It allows events to be filtered by:
application type (Kea, BIND 9)
daemon type (DHCPv4, DHCPv6,
the user who caused given event (available only to users in the