Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 220
    • Issues 220
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & 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 Projects
  • storkstork
  • Issues
  • #390
Closed
Open
Created Sep 01, 2020 by Vicky Risk@vickyDeveloper

UI review ticket: don't display subnets for machines that are not currently monitored

When the user disabled monitoring on the agent-kea6 application, the subnets on that application did not disappear from the subnets list. The same occurred with turning off monitoring for a DHCPv4 daemon. Utilization numbers on the subnets on this application that was not supposed to be monitored kept updating in Stork. This seems like a bug.

If the subnet is present on multiple machines, and some of those machines are actively being monitored, then of course, it is fine to display the subnet.

This user commented that he might turn off monitoring on some machines to simplify the interface to narrow the scope of what he was monitoring and that doesn't work if information from unmonitored machines is not filtered out.

Assignee
Assign to
Time tracking