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.

Downtime Manager

The Opsview Downtime Manager purpose is to:

• Receive downtime requests from the orchestrator API:
  • Plan a new downtime.
  • Cancel a current or future downtime.
• Maintain the downtime status of services, host, and downtime history.

Dependencies Copied

This component requires access to the opsview MySQL database, to the Opsview Message Queue and the Opsview DataStore.

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

Installation Copied

Refer to Advanced Automated Installation.

Configuration Copied

We ship the opsview-downtimemanager with its default configuration, which can be modified or overridden by the user.

• default setting: /opt/opview/downtimemanager/etc/downtimemanager.defaults.yaml
• custom setting example: /opt/opsview/downtimemanager/etc/downtimemanager.yaml.example
• user settings: /opt/opview/downtimemanager/etc/downtimemanager.yaml

Default settings are restored on upgrade/installation, user settings are left as defined by the user. The setting files follow the YAML file format; setting are stored in a <setting_name>: format.

The custom setting example contains an example on how to override default value.

Configuration options Copied

• runtime_database: configuration for the Runtime database.
• downtime_queue: the message-queue configuration to receive downtime messages.
• downtime_store: the data-store configuration.
• registry: connection configuration for the Registry.
• logging: component logging configuration.

Management Copied

Configuration Copied

DPKGs Copied

Watchdog service files are now managed by the package, doing a remove would leave the watchdog service file behind with a .save extension. Purging the package will remove it. The package managed config files:

RPMs Copied

Watchdog service files are now managed by the package. Any modifications will be saved at upgrade and remove processes with the .rpmnew and .rpmsave extenstions correspondingly.

Service Administration Copied

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