The Opsview results performance component processes performance results and passes them on to the Timeseries component.
Opsview Time Series
Refer to Advanced Automated Installation.
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.
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
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:
Manually restore the file with the rpmsave extension.
Rename the rpmnew to the config file name if they want to use the new config for the package.
As root, start, stop and restart the service using:
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-resultsperformance
Updated almost 3 years ago