Welcome to docs.opsview.com

Installation prerequisites

This page describes some prerequisites that should be followed before installation of the Opsview software.

Note that package installation of Opsview will bring in other dependent software. However, some of the tasks below may require the dependent software to be installed first.

Note: You should not install NagiosĀ® Core separately as Opsview uses its own version.

Obtain an Opsview subscription

To use Opsview 4 you will need a valid subscription. You will receive your software key from Opsview when you purchase your Opsview subscription.

Please read our documentation on managing your Opsview subscription.


Opsview is distributed via repositories. While we recommend you use the latest repository, you can track a major release version instead.

For instance, https://downloads.opsview.com/opsview-commercial/4.2/ will track the most recent version of 4.2, whereas https://downloads.opsview.com/opsview-commercial/latest/ will track whichever is the most recent release of Opsview.

You can use the above URLs where the installation instructions refer to the repository location.

Opsview server

Users and groups

The Opsview installation package will create the required users and groups if they do not currently exist.

However, if you wish to create the user groups yourself and be sure they exist first, instructions follow.

Note: You cannot use different usernames or group names.

Create the following user and groups:

User Group
opsview opsview
nagios nagios, nagcmd

If you use an external authentication system, you may need to make some changes to local user and group files. We recommend that you have these users and groups set up locally to remove the dependency on an external system.

Your web server user will also need to be in the nagcmd group.

Note: The nagios user needs to have write access to its home directory. The installation process will update the .profile (or .bash_profile) file in the nagios user's home directory in order to source the file /usr/local/nagios/bin/profile, which is required to set up some Opsview environment variables. If this is not set up on your system, you can run /usr/local/nagios/installer/set_profile as the nagios user to do it for you.


Supported versions

Opsview supports MySQL version 5.0.x, 5.1.x and 5.5.x. We run tests against the latest version of MySQL on each supported platform, as distributed by the OS vendor.

MySQL 6 is not currently supported.


We recommend that you install MySQL prior to installing Opsview so that you can tune it before Opsview creates its databases.

Please make a note of your MySQL root password, as you will be prompted for this during Opsview installation.

Opsview uses a mixture of MyISAM and InnoDB engine types. For manageability, we recommend you make the following changes in the mysqld section of my.cnf before installing Opsview. Note, you will have to restart MySQL for these to take effect.

innodb_file_per_table = 1
innodb_flush_log_at_trx_commit = 2

innodb_flush_log_at_trx_commit = 2 caches transaction changes so that database changes are flushed once per second, instead of per transaction. See the MySQL documentation for more details.

On a dedicated MySQL server, you should set the innodb_buffer_pool_size as large as possible, leaving around 40% free memory for the OS:

innodb_buffer_pool_size = 1G

On a server that also runs Opsview, you should not set innodb_buffer_pool too high as Opsview will require memory to run all its checks and to serve the dynamic web pages. Over allocation of memory to MySQL will cause it to use swap memory, which slows the whole server dramatically. Ensure there is at least 80% free memory outside of MySQL for shared servers.

It may be desirable to disable MySQL binary logging. If this is left enabled, it is recommended that the amount of free disk space is monitored.

See the MySQL tuning pages for more recommendations.


Opsview has several jobs that are used by cron for the nagios user. Ensure that cron is installed and active.