So would this then be:

1. Add job / modify existing jobs to use script from Write a contrib script that serves as a proof-of-concept of such an integration with the ISC DHCP server. #2371 to collect DHCP stats
2. Add 3 graphs to /search/vlan/xxxx for max/cur/touch that show the DHCP stats

And does Summary refer to the dashboard? if so im guessing this button solves that:

So would this then be:

1. Add job / modify existing jobs to use script from [Write a contrib script that serves as a proof-of-concept of such an integration with the ISC DHCP server. #2371](https://github.com/Uninett/nav/issues/2371) to collect DHCP stats

No. There is no need for NAV-jobs to run this script. A user who wants to get their DHCP stats into will need to grab this contrib script and install it as a cronjob on their DHCP server (normally not the same as the NAV server). There it will parse the output of the dhcpd-pools command and push data to the same Graphite server NAV uses.

The requirement for said script is that it sends the metrics using a path structure that NAV can understand and get meaning (i.e. VLAN ids) from.

However, you might want actual data to test on - which is where you would want to set up this contrib script on one of our DHCP servers to export stats to your development instance.

2. Add 3 graphs to /search/vlan/xxxx for max/cur/touch that show the DHCP stats

All three values plotted on a single graph will do (much in the same vein existing IP address utilization graphs on that page are made).

And does Summary refer to the dashboard? if so im guessing this button solves that:

I'm not sure what I meant by and to summary 😆 The issue title comes from a bullet point that was automatically converted to an issue by GitHub - that doesn't always translate to make sense as an issue title. I'm removing it, and hoping it will come back to me later what I was thinking 😄