@Aram, I’d say yes and no.
To me, a WatchDog should be be external service to the BESClient and provide more than simple up/down monitoring. This WatchDog service should help monitor the general health of the local BESClient installation and when/where possible take corrective action. It should also prevent users with elevated permissions from disabling or otherwise tampering with the BESClient installation.
I think with the BESClient compliance API this should be relatively possible.
Finally, I can provide specific NIX use case details if you’re interested.