Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 555
    • Issues 555
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 66
    • Merge requests 66
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #755
Closed
Open
Issue created Jul 29, 2019 by Marcin Siodelski@marcinDeveloper

Kea DHCP servers' observations should be reset to some initial values upon restart or reconfiguration

While setting up the test environment of Kea with Prometheus we have discussed that various observations exposed by Kea should be set to initial values when the server is started. One use case is that you start the Kea server which doesn't receive any traffic before you set queries in Prometheus/Grafana. Currently, Kea performs lazy initialization of the statistics such as pkt4-received etc. Therefore, the Kea exporter would not know which statistics is supported by Kea, because this statistics would not be returned before the traffic is sent to the Kea server.

It is not practical to set default values in the Kea exporter, because it would be hard to keep it with sync with the statistics supported by Kea.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking