Results Performance

The Opsview results performance component processes performance results and passes them on to the Timeseries component.

Dependencies Copied

Opsview Time Series.

Installation Copied

Refer to Advanced Automated Installation.

Configuration Copied

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

• default setting: /opt/opview/resultsperformance/etc/resultsperformance.defaults.yaml
• custom setting example: /opt/downtime/resultsperformance/etc/resultsperformance.yaml.example
• user settings: /opt/opview/resultsperformance/etc/resultsperformance.yaml

Default setting 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 on a <setting_name>: format.

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 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.

Service administration Copied

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