The Opsview Autodiscovery Manager its used for discovering devices set up on your network for more easily adding monitoring of devices into Opsview
It uses the python binary provided in
This component is deployed on the Master server when installating Opsview Monitor and must not be moved to another server.
Any user configurations should be created in the /opt/opsview/autodiscoverymanager/etc/autodiscoverymanager.yaml
Watchdog service files are now managed by the package manager, removing the package would leave the watchdog service file behind with a .save extension. Purging the package will remove it. The package manager managed config files are as follows
Watchdog service files are now managed by the package manager. When removing the package, if the files listed have been modified by the user before; they will be left behind after rpmsave extension has been added to them. When upgrading the package, if the files listed have been modifed by the user before; the modified file on the disk will remain and the new config file from the upgrading package will be written to the disk with the rpmnew extension. Users will have to:
Manually restore the file with the rpmsave extension.
Rename the rpmnew to the config file name if they want to use the new config for the package.
As root, start, stop and restart the service using:
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-autodiscoverymanager
Updated almost 4 years ago