mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-31 14:05:33 +00:00
Code Issues Releases Wiki Activity

[755-Kea-DHCP-servers-observations-should-be-reset] implement required changes to dhcp4 and dhcp6 servers

Browse Source
This commit is contained in:
Franciszek Gorski
2019-09-05 09:35:19 +02:00
committed by Marcin Siodelski
parent 61cda1b5e1
commit 3a92d22727
7 changed files with 66 additions and 76 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/sphinx/arm/dhcp4-srv.rst
View File

@@ -5510,6 +5510,10 @@ following statistics-related commands:
- statistic-get-all
- statistic-reset-all
- statistic-remove-all
- statistic-sample-age-set
- statistic-sample-age-set-all
- statistic-sample-count-set
- statistic-sample-count-set-all
as described in :ref:`command-stats`.

4
doc/sphinx/arm/dhcp6-srv.rst
View File

@@ -5524,6 +5524,10 @@ following statistics-related commands:
- statistic-get-all
- statistic-reset-all
- statistic-remove-all
- statistic-sample-age-set
- statistic-sample-age-set-all
- statistic-sample-count-set
- statistic-sample-count-set-all
as described in :ref:`command-stats`.

37
doc/sphinx/arm/stats.rst
View File

@@ -52,15 +52,16 @@ for a list of statistics-oriented commands.
Statistics Lifecycle
====================
It is useful to understand how the Statistics Manager module works. When
the server starts operation, the manager is empty and contains no
statistics. If the ``statistic-get-all`` command is executed at that point, an empty list is
returned. Once the server performs an operation that causes a statistic
to change, the related statistic will be created. In general, once a
statistic is recorded even once, it is kept 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.
It is useful to understand how the Statistics Manager module works.
Since Kea 1.7.0 when the server starts operation, the manager contains
all statistics related to runned type of DHCP server, initialized with
default value. If the ``statistic-get-all`` command is executed at that point,
a list with these statistics is returned. Once the server performs an operation
that causes a statistic to change, the related statistic will be created or updated.
In general, once a statistic is recorded even once, it is kept 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.
Statistics are considered runtime properties, so they are not retained
after server restart.
@@ -84,14 +85,16 @@ Commands for Manipulating Statistics
There are several commands defined that can be used for accessing
(-get), resetting to zero or a neutral value (-reset), or removing a
statistic completely (-remove). The difference between reset and remove
is somewhat subtle. The reset command sets the value of the statistic to
zero or a neutral value, so after this operation, the statistic will
have a value of 0 (integer), 0.0 (float), 0h0m0s0us (duration), or ""
(string). When requested, a statistic with the values mentioned will be
returned. ``Remove`` removes a statistic completely, so the statistic
will no longer be reported. Please note that the server code may add
it back if there is a reason to record it.
statistic completely (-remove). We can change the statistics time based
limit (-sample-age-set) and size based limit (-sample-count-set).
The difference between reset and remove is somewhat subtle.
The reset command sets the value of the statistic to zero or a neutral value,
so after this operation, the statistic will have a value of 0 (integer),
0.0 (float), 0h0m0s0us (duration), or "" (string).
When requested, a statistic with the values mentioned will be returned.
``Remove`` removes a statistic completely, so the statistic will no longer
be reported. Please note that the server code may add it back if there is a reason
to record it.
.. note::