Opsview 6.9.x End of Support

Opsview versions 6.9.x reached their End of Support (EOS) status at the end of January 2026, in accordance with our Support policy. As of this date, these versions no longer receive code fixes, security updates, maintenance releases, or backported changes.

The documentation for version 6.9.7 and earlier releases will remain accessible for reference, but it will no longer be updated or maintained. We strongly recommend upgrading to the latest supported version of Opsview to ensure continued support and access to the latest features and security enhancements.

BSM

The Opsview BSM is a business service monitoring module.

Dependencies Copied

It uses the python binary provided by opsview-python3.

You will also need to ensure the mysql client binary is installed.

Installation Copied

Refer to Advanced Automated Installation.

Configuration Copied

Any user configurations should be created in the /opt/opsview/bsm/etc/bsm.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 files are as follows:

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: