Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 318
    • Issues 318
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • 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
  • storkstork
  • Issues
  • #252

Stork needs to show LPS statistic

With the completion of #226 (closed) we now have a dashboard that shows subnets and pool utilization. We should extend it with leases per second statistic. Here's a mockup made by @godfryd how this could possibly look like.

dashboard-mockup

The ability to show it in the last 5 or 15 mins and some larger timescale (24h maybe) would be very useful.

This will require some small design. Here's couple caveats that's worth considering:

  • should we keep the historic (last 24h) data in stork or in kea?
  • what if Kea is restarted?
  • if we implement something new in Kea, how can this work with older Kea releases?
  • Kea doesn't have explicit LPS statistic, but has the ability to store multiple observations of addresses-assigned with timestamp. This can be used to estimate LPS. But is it precise enough? If there's a lot of traffic, the observations are only split second apart. If there's no traffic at all, there are no observations.
  • Kea has a mechanism for storing multiple observations. If it's useful, perhaps we could use it. If not, maybe we could get rid of it altogether?
Assignee
Assign to
Time tracking