Opsview 6.8.x End of Support

With the release of Opsview 6.11.0 on February 2025, versions 6.8.x have reached their End of Support (EOS) status, according to our Support policy. This means that versions 6.8.x will no longer receive code fixes or security updates.

The documentation for version 6.8.9 and earlier versions will remain accessible for the time being, but it will no longer be updated or receive backports. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.

Autodiscovery Manager

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

Dependencies Copied

It uses the python binary provided in opsview-python3.

Installation Copied

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

Configuration Copied

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

Management Copied

Configuration Copied

DPKGs Copied

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 file:

RPMs Copied

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 modified 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 :

Service administration Copied

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