Welcome to docs.opsview.com

Automated installation

Automated installation is our recommended way of installing Opsview, as it is the quickest and easiest way of getting from sign-up to monitoring! Note, this installation process is only applicable for the following platforms:

  • Debian 6 and 7
  • Ubuntu 12.04 and 14.04
  • Centos 6 and 7
  • Redhat 5, 6 and 7
  • SLES 11 SP3

Automated installation is designed for use on fresh Operating System installs, any existing packages or configuration could be overwritten or removed during the Opsview install process.

The automated installation script will:

  • Set up opsview package repositories and additional repositories required by your system.
  • Install and configure the prerequisites.
  • Configure your operating system in preparation to installing Opsview.
  • Update your installed packages to the latest version.
  • Install Opsview and run post-installation tasks.
  • Depending on your Opsview subscription, ask if it should install and configure any additional modules (Network Analyzer, ServiceDesk Connector or Reporting).
  • Set up the admin account.

Please note that this method does not support upgrading Opsview or its modules. To upgrade, please refer to the manual upgrade section of the wiki for your platfform.

The automated installation method will always install the latest available version of Opsview. As of October 14th 2015, this method will install Opsview Monitor version 5.0, not 4.6

Before you start

  • Make sure you have your software key and repository key available, they should have been sent to you via email. If not, please contact your account manager, raise a support incident via our support portal or contact us, and we will be able to quickly help you out.
  • If you are new to Opsview and do not have a subscription or an active trial, you can quickly get a trial software key and repository key using the following link.

All systems

It might be that your system lacks the required commands: sudo, lsb_release or curl, you can install them as root using:

  • Debian/Ubuntu:
    apt-get -y install sudo curl lsb-release
  • RedHat/CentOS:
    yum -y install sudo curl redhat-lsb-core
  • SLES:
    zypper install lsb-release

    (sudo and curl come preinstalled, even on a minimal system)

RedHat 5

Please upgrade your openssl first, to be able to validate the SSL certificate.

sudo yum -y install openssl

RedHat 6

If RHN Optional Channel is not already enabled you will be prompted for your RHN username and password to activate it.


There is an issue with libopenssl on SLES. Please see the note on the SLES installation page.


See our design notes for further information on planning for separate database servers, disk partitioning and security.


Run this command first:

curl -L https://install.opsview.com | sudo bash

You will be prompted for your software key and repository key.


You can provide the software key and repository key to the command as follows

curl -L https://install.opsview.com | sudo bash -s -- -r $REPOSITORY_KEY -e $SOFTWARE_KEY

You will also be prompted for a password that will be used for both your Opsview admin username, and also the MySQL root password. Don't worry - this can be easily changed in the future if you change your mind!

Local or remote database

During the installation process of Opsview and/or modules, you will be asked if you want to use a local or remote database. Usually, Opsview and its modules are installed locally. If you choose to use a remote database, you will be asked for connection details for it. If you wish the module databases to be split (remote/local) from Opsview, you will have to run the install command separately for each situation.

We highly recommend the Reports database be installed on the same server as Opsview. This is because Opsview installs ODW locally, so it makes sense to have these databases on the same server for performance reasons. If you do want to have Reports on a different server, the automated process will allow that, but you will have to let JasperServer know this, post-installation. Reports won't be able to generate any reports until then.

When installing Opsview on a database that does not have a root password, you will be prompted to set one. This will become both your MySQL root password and the password of the Opsview's admin account. When installing modules only, the MySQL root password won't be changed.

Installing modules

Opsview modules can be installed separately or together by using the -m flag:

curl -L https://install.opsview.com | sudo bash -s -- -m

You will be asked to install each module individually, if you are licensed for them.

Logging in

Once Opsview has been installed, log on using the password you set during installation, after which you can start monitoring and enjoying your new Opsview system! Also, check out our quick start guide to help you get familiar with Opsview, along with various other resources you may find useful in your journey to becoming an Opsview guru:

Uninstalling Opsview

All of Opsview, including its modules, can be removed with the -u flag:

curl -L https://install.opsview.com | sudo bash -s -- -u

You will be asked if you want to remove Opsview's configuration, log files, etc. The Opsview database will not be removed, in case you wish to retain its data. If you want to remove it manually, issue these commands as the MySQL root user:


We do not recommend the use of this flag.

Uninstalling modules only

Opsview modules can be uninstalled separately or together by using the -n flag:

curl -L https://install.opsview.com | sudo bash -s -- -n

You will be asked to uninstall each module. However, any module specific database will not be removed, in case you wish to retain its data.


Cancelling the installation

You can abort the installation process at any step and manually remove any packages installed in the process.

Continuing aborted installation

Your action will depend at what stage the installation process has been aborted - error messages will be displayed during the installation process.

If any Opsview packages are in broken state - remove them.

If any other packages are in broken state, try reinstalling them or simply remove them.

Remove any Opsview databases installed in the process.

When your system is stable again, run the installation process again. Any files will be overwritten in the process.

Using a proxy server

If you are using a proxy, you may need to add a line into ”/etc/apt/apt.conf” (on Ubuntu/Debian, for example) with the following content:

Acquire::http::Proxy::downloads.opsview.com "http:<IP>:<port>";

This will differ for YUM, where you will need to edit the file ”/etc/yum.conf” with the following content: