Hey! These docs are for version 6.4, which is no longer officially supported. Click here for the latest version, 6.7!


## Description

This component is built using python, which will read stats from the state change message queue and push them on to the database.

## Dependencies

Registry, Messagequeue, Core-utils. Please make sure these are installed, configured and running before attempting to start the opsview-statechanges process.

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

## Installation

Refer to [Advanced Automated Installation](🔗).

### Configuration

Default statechanges yaml file contains information about database and messagequeue connections, If users want to point to a non default server they should create a statechanges.yaml file and provide the information in there.

## Management

### Configuration

#### DPKGs

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

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

#### 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-state-changes.conf

### Service Administration

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