Our software repositories will include the following packages in source form:

  • **[deprecated]** opsview-agent

  • opsview-external

  • opsview-jasper

  • opsview-monitoring-scripts-base

  • opsview-netaudit-external

  • opsview-perl-external

  • opsview-timeseries-influxdb

  • opsview-watchdog

Note - opsview-agent contains the Opsview Linux Agent, and is now deprecated.

## Accessing Source Packages

To access a source package, you will need to setup the Opsview repository and then download the package based on the OS. The instructions below assume opsview-watchdog, but you can replace with any of the packages above.

## Creating and Modifying Source Packages

You can build from the source packages based on your OS by following the instructions below. This will compile the original third party software, apply our changes to them and create a package, either debian or RPM, for installation.


Opsview Ltd does not test nor support packages created in this way.

#### Debian Source Packages

On a fresh Debian system:

  • `sudo apt-get update`

  • `sudo apt-get install build-essential fakeroot devscripts debhelper`

    • If building opsview-external, also run `sudo apt-get install python2.7-dev`

  • Add our repository:

  • `sudo apt-get update`

  • `sudo apt-get install opsview-setup`

  • Update apt sources to include the sources repository list by editing `/etc/apt/sources.list.d/opsview.list` and changing `deb` to `deb-src`

  • `sudo apt-get update`

  • As a **non-root user**, run `apt-get source opsview-watchdog`, which will download and expand the source package in your current directory

  • `cd opsview-watchdog-*`

  • Now run `make package`

  • Additional build dependant packages may be required.

  • On Ubuntu 18 systems, if `/usr/bin/python2` is not present, this step may fail. In that case, you can create a symlink: `sudo ln -s /usr/bin/python2.7 /usr/bin/python2` to proceed with package building. You will have the deb file in the directory above.

#### RPM Source Packages

On a fresh RPM platform:

  • `sudo yum install rpm-build redhat-rpm-config perl-TimeDate yum-utils`

  • If building `opsview-external`, also run `sudo yum install python-devel`

  • Add our repository:

  • `sudo yum install opsview-setup`

  • `yumdownloader --source opsview-watchdog` to download the \*.src.rpm file

  • `sudo rpmbuild --define "__arch_install_post /bin/true" --rebuild *.src.rpm` will have RPMs built in `/root/rpmbuild/RPMS/x86_64/.`

  • Additional build dependant packages may be required.

  • You may need to install [EPEL](🔗) for these dependencies.

## Plugins

In addition to the source packages listed above, the opsview-opspacks package contains the following third-party plugins within Opspacks:

  • database-microsoft-sql.tar.gz

    • [check_mssql_database](🔗)

  • san-netapp.tar.gz

    • [check_netapp3.pl](🔗)

  • application-dell-hardware.tar.gz

    • [check_openmanage](🔗)

  • database-oracle-rdbms.tar.gz

    • [check_oracle_health](🔗)

  • os-vmware-vsphere-host.tar.gz

    • [check_vmware_api](🔗)

  • os-windows-winrm-base-agentless.tar.gz

    • [check_windows_updates.ps1](🔗)

  • os-windows-wmi-base-agentless.tar.gz

    • [check_wmi_plus](🔗)

To download the source and modifications made to these plugins follow the instructions below. Any patches to plugins that Opsview has produced are automatically applied as part of the distribution of Opspacks.

### Install opsview-opspacks package

You will need to install opsview-opspacks to get the instructions and bring in other dependencies before you can apply changes

#### Setup Opsview Repositories

#### Centos/RHEL/OL

Update yum and install opsview-opspacks

#### Debian/Ubuntu

Update apt and install opsview-opspacks:

### Extract plugin

Extract the package for the Opspack you want to view. e.g. database-oracle-rdbms.tar.gz

Follow the instructions found in the `README.md` file to patch the plugin file(s). If there isn't a `README.md` or a patches directory, then Opsview has not made any patches to the plugin.