These docs are for v6.6. Click to read the latest docs for v6.7.

Description

Opsview watchdog is a process management component. It manages the starting, stopping and restarting of opsview components. It is a dependency of every opsview components which is required to run a process to operate. The process is launched by opsview watchdog and it monitors the process it has launched. If the process dies or stops abruptly, Watchdog will try to restart the process and log errors in syslog.

Dependencies

The Watchdog installs opsview-agent package.

Installation

This is deployed when installing Opsview Monitor.

Configuration

Run opsview-watchdog using the following command

sudo /opt/opsview/watchdog/bin/opsview-monit
# on system reboot watchdog will start itself automatically

Management

Configuration

DPKGs

Watchdog service files are now managed by the package manager, removing the package would leave the watchdog service file behind. Purging the package will remove it. The package manager managed config files are as follows

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

  • /opt/opsview/watchdog/etc/monitrc

RPMs

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.

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

  • /opt/opsview/watchdog/etc/monitrc

Service Administration

Start, stop and restart the service using:

sudo systemctl <start|stop|restart> opsview-watchdog