ITRS Opsview Cloud Documentation

License Manager

The Opsview License Manager enables the licensed features of Opsview Monitor. Licenses are locked to the machine’s hostname and its network MAC address — if any of those two change the system needs to be re-licensed.

Dependencies Copied

This component is required by Master Orchestrator server.

Installation Copied

This component is deployed on the Master server when installing Opsview Monitor and must not be moved to another server.

Configuration Copied

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

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.

Configuration options Copied

Management Copied

Configuration Copied

DPKGs Copied

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


RPMs Copied

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.


Service Administration Copied

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

/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-licensemanager
["Opsview On-premises"] ["User Guide"]

Was this topic helpful?