Source Packages

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

• opsview-external
• opsview-jasper
• opsview-monitoring-scripts-base
• opsview-netaudit-external
• opsview-perl-external
• opsview-python3-modules (for this package, follow separate instructions at the bottom of the page)
• opsview-timeseries-influxdb
• opsview-watchdog
• opsview-agent

Note: The opsview-agentcontains the Opsview Linux Agent.

Accessing Source Packages Copied

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 (except opsview-python3-modules).

Creating and Modifying Source Packages Copied

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.

Note

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

Debian Source Packages Copied

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:

  curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -O repo
  

• 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 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 Copied

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 (on RHEL8/OL8, sudo yum install python2-devel)
• Add our repository:

  curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -O repo
  

• 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 Copied

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 Copied

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

Setup Opsview Repositories Copied

curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -O repo

Centos/RHEL/OL Copied

Update yum and install opsview-opspacks:

sudo yum makecache fast
sudo yum install opsview-opspacks

Debian/Ubuntu Copied

Update apt and install opsview-opspacks:

sudo apt-get update
sudo apt-get install opsview-opspacks

Extract plugin Copied

Extract the package for the Opspack you want to view. For example, database-oracle-rdbms.tar.gz.

tar -zxvf /opt/opsview/monitoringscripts/opspacks/<name_of_opspack>.tar.gz
cd <name_of_opspack>

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.

Accessing the opsview-python3-modules source package Copied

You can access the source code for the opsview-python3-modules package and apply our modifications to the code by following the instructions below.

Debian system Copied

On a fresh Debian system:

• sudo apt-get update
• sudo apt-get install build-essential fakeroot devscripts debhelper
• Add our repository:

curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -O repo

• 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-python3-modules, which will download and expand the source package in your current directory,
• cd opsview-python3-modules-*
• Source code and patch files can be viewed within this directory structure.
• Run make patches-external to apply all modifications - patched libraries will be present in build/index as tar.gz archives.
• Additional dependant packages may be required.

RPM system Copied

On a fresh RPM platform:

• sudo yum install rpm-build redhat-rpm-config perl-TimeDate yum-utils
• Add our repository:

curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -O repo

• yumdownloader --source opsview-python3-modules to download the *.src.rpm file
• Turn this into a tar.gz archive with rpm2cpio opsview-python3-modules-*.src.rpm | cpio -id and extract the archive with tar -xzf opsview-python3-modules-*.tar.gz
• cd opsview-python3-modules-*
• Source code and patch files can be viewed within this directory structure.
• Run make patches-external to apply all modifications - patched libraries will be present in build/index as tar.gz archives.
• Additional dependant packages may be required.