Results Live


Opsview Results Live component maintains and updates state information in the database and couchdb Datastore. It is also responsible for forwarding state information about Acknowledgements and Downtime. It also handles broadcast messages to be sent out for the virtual hosts.


This component requires access to the opsview MySQL or MariaDB database, to the Opsview Message Queue and the Opsview DataStore. Please make sure opsview-core-utls, opsview-messagequeue and opsview-datastore are installed configured and running before attempting to install and configure opsview-results-live.

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


Refer to Advanced Automated Installation.


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

  • default setting - /opt/opview/resultslive/etc/resultslive.defaults.yaml

  • custom setting example - /opt/downtime/resultslive/etc/resultslive.yaml.example

  • user settings - /opt/opview/resultslive/etc/resultslive.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.

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




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 are as follows

  • /opt/opsview/watchdog/etc/services/opsview-resultslive.conf


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

  • /opt/opsview/watchdog/etc/services/opsview-resultslive.conf

Service Administration

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

/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-resultsive