New Installation

Learn how to install Opsview Monitor and its components

Welcome to the Opsview Monitor New Installation guide.

If you already have an instance of Opsview Monitor, then check the following pages instead depending on whether you want to perform an automated in-place upgrade or a migration to new hardware.

For brand new installation:

  • Firstly, please take a few minutes to review the Release Notes before you start. Opsview Monitor release makes use of the standard software license key.

  • Next, it's important that you have reviewed the Prerequisites, to ensure that any software and hardware dependencies, along with any limitations, are fully understood prior to installation.

Please follow the Automated Installation guide for an automated installation from the package repositories on to a server that you have pre-configured with your choice of supported operating system.

Documentation Conventions


All commands should be run as the opsview user, unless otherwise documented. For all commands that should be run with higher privileges the documentation prefixes the commands with sudo or specifically states to switch to the appropriate user (note: some local password policies may require you to enter a password when using sudo - this is not shown in our documentation).


The following sections show the commands to be run in a highlighted format, such as /path/to/command -o options or in a separate block:

/path/to/command -o options

Some code blocks also include example output, such as:

$ /path/to/command -o options
output line1
output line2
output line3

Or the following for running via sudo:

$ sudo /path/to/command -o options
root command output line1
root command output line2
root command output line3

Commands may be copied from these blocks and pasted as appropriate.

Configuration files

Configuration files are shown within blocks, such as this YAML format file:

            always_update_metadata: false
            workers: 4
    # Directory to store rrd database files
    data_dir: /opt/opsview/timeseriesrrd/var/data
    # Days to keep non-updated rrd files
    retention_days: 30


YML Config Files

TIP: Indentation using sets of 4 space characters is critical in these files;
Do not use <TAB> characters as this can lead to spurious errors.