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

## Description

Registry provides the Service Discovery capabilities to Opsview. At least one copy of the package has to be installed in case of single-node cluster. It can be installed on any server that is reachable from all the other servers - see [Ports](🔗). When part of the cluster, it will exchange heartbeats with other nodes every 0.1s (configurable).

## Dependencies

Registry Proxy provides access to the Registry component using Loadbalancer. Please make sure you have the loadbalancer installed, configured and running before attempting to start the opsview-registry process

## Installation

Refer to [Advanced Automated Installation](🔗).

## Configuration

We ship the `opsview-registry` with a default configuration which can be modified or overridden by the user.

  • **default setting** - /opt/opview/registry/etc/registry.defaults.yaml

  • **custom setting example** - /opt/opsview/registry/etc/registry.yaml.example

  • **user settings** - /opt/opview/registry/etc/registry.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>: <value> format.

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

### Configuration options

  • data_dir: Path to the data directory

  • wal_dir: Path to the dedicated wal directory, this allows a dedicated disk to be used, and helps avoid io competition between logging and other IO operations.

  • snapshot_count: Number of committed transactions to trigger a snapshot to disk

  • heartbeat_interval: Time (in milliseconds) of a heartbeat interval

  • election_timeout: Time (in milliseconds) for an election to timeout

  • listen_peer_port: Port to listen on for peer traffic.

  • listen_client_port: Port to listen on for client traffic.

## Management

### Configuration

#### DPKGs

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

  • /opt/opsview/loadbalancer/etc/registry-proxy.cfg

#### RPMs

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

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

  • /opt/opsview/loadbalancer/etc/registry-proxy.cfg

### Service Administration

Restarting/stopping registry will trigger a failure in the majority of Opsview Monitor components!

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