These docs are for v6.6. Click to read the latest docs for v6.7.

Autodiscovery Manager

Description

The Opsview Autodiscovery Manager its used for discovering devices set up on your network for more easily adding monitoring of devices into Opsview

Dependencies

It uses the python binary provided in opsview-python3.

Installation

This component is deployed on the Master server when installating Opsview Monitor and must not be moved to another server.

Configuration

Any user configurations should be created in the /opt/opsview/autodiscoverymanager/etc/autodiscoverymanager.yaml

Management

Configuration

DPKGs

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

  • /opt/opsview/watchdog/etc/services/opsview-autodiscoverymanager.conf

RPMs

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:

  1. Manually restore the file with the rpmsave extension.

  2. Rename the rpmnew to the config file name if they want to use the new config for the package.

  • /opt/opsview/watchdog/etc/services/opsview-autodiscoverymanger.conf

Service Administration

As root, start, stop and restart the service using:

/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-autodiscoverymanager