FWIW we also primarily use Monit to keep tabs on the Kea daemons in our
environment. Because we're using MySQL backends, the Monit watchdog can
safely restart the daemon if it crashes or becomes unresponsive.
There is an external watchdog service we use to check the process table for
the daemon as
I had a thought regarding how you could implement some sort of monitoring
solution for DHCPv6. I don’t think you could implement a client but it should
be possible to pretend to be a relay agent to perform a monitoring function for
DHCPv6 like I described for DHCPv4. I think that is the way th
One way to monitor is with Stork. It won't alert you, but it does have an API
that collects events such as failure to communicate with a daemon using the Kea
control agent, or HA state changed. One can poll that API and emit alerts based
on the interesting events. Stork agents also have Promethe
What we did, 20+ years ago, was implement a rudimentary DHCPv4 client in perl
as a module for the monitoring software we use. We only implemented “renew”
functionality. On all of the DHCP servers that we wanted to monitor, we had
the subnet of the monitoring cluster configured as a pool. Then
