summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarcin Siodelski <marcin@isc.org>2019-09-06 12:28:29 +0200
committerMarcin Siodelski <marcin@isc.org>2019-09-06 12:28:29 +0200
commitbd429574579b12d4779bf610e47be90058525c8b (patch)
tree4cb596bfea40b7fc88c49d7a2a12c54c37994be0
parent[#755,!502] Removed duplicated test after the rebase. (diff)
downloadkea-bd429574579b12d4779bf610e47be90058525c8b.tar.xz
kea-bd429574579b12d4779bf610e47be90058525c8b.zip
[#755,!503] Small editorial changes in the stats.rst.
-rw-r--r--doc/sphinx/arm/stats.rst13
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/sphinx/arm/stats.rst b/doc/sphinx/arm/stats.rst
index 76c66f34a8..353be8d299 100644
--- a/doc/sphinx/arm/stats.rst
+++ b/doc/sphinx/arm/stats.rst
@@ -53,19 +53,20 @@ Statistics Lifecycle
====================
In Kea 1.6.0 version and earlier, when the Kea server is started some
-of the statistics are initially not returned. For example, the ``pkt4-received``
-statistic is not initialized until the first DHCP packet is received.
+of the statistics are initially not initialized. For example, the ``pkt4-received``
+statistic is not available until the first DHCP packet is received.
In the later Kea versions, this behavior has been changed and all of the
-statistics supported by the servers is initialized upon the servers' startup
+statistics supported by the servers are initialized upon the servers' startup
and should be returned in response to the commands such as
``statistic-get-all``. The runtime statistics concerning DHCP packets
-processed is initially set to 0 and is not retained across the server
-restarts.
+processed is initially set to 0 and is reset upon the server
+restart.
+
+Per-subnet statistics are recalculated when reconfiguration takes place.
In general, once a statistic is initialized it is held in the manager until
explicitly removed, by ``statistic-remove`` or ``statistic-remove-all``
being called, or when the server is shut down.
-Per-subnet statistics are explicitly removed when reconfiguration takes place.
Removing a statistic that is updated frequently makes little sense, as
it will be re-added when the server code next records that statistic.