with timeouts. The default timeout value is set to 10 seconds and is not
configurable.
+This API can be used by external tools to manage and monitor Kea operation.
+An example of such a monitoring tool is ISC Stork. For details, see
+:ref:`stork`.
+
.. _ctrl-channel-syntax:
Data Syntax
...
}
+Statistics can be retrieved periodically to gain more insight into Kea operations. One tool that
+leverages that capability is ISC Stork. See :ref:`stork` for details.
+
.. _dhcp4-ctrl-channel:
Management API for the DHCPv4 Server
...
}
+Statistics can be retrieved periodically to gain more insight into Kea operations. One tool that
+leverages that capability is ISC Stork. See :ref:`stork` for details.
+
+
.. _dhcp6-ctrl-channel:
Management API for the DHCPv6 Server
Kea Netconf configuration file: /usr/local/etc/kea/kea-netconf.conf
keactrl configuration file: /usr/local/etc/kea/keactrl.conf
+``keactrl status`` reporting capabilities are rather basic. If you need more extensive insight
+into the Kea health and status, you may consider deploying Stork. For details, see :ref:`stork`.
+
.. _keactrl-overriding-servers:
Overriding the Server Selection
The details of ``keactrl`` script usage can be found in :ref:`keactrl`.
+Once you have Kea services up and running, you may consider deploying a dashboard solution
+that would monitor running services. For more details, see :ref:`stork`.
+
.. _quick-start-direct-run:
Running the Kea Servers Directly
single statistic or all statistics. See the section :ref:`command-stats`
for a list of statistics-oriented commands.
+Statistics can be used by external tools to monitor Kea. One example of such a tool is Stork.
+See :ref:`stork` for details how to use it to retrieve statistics periodically (and use
+other data sources) to get better insight into Kea health and operational status.
+
.. _stats-lifecycle:
Statistics Lifecycle