Source Packages

The Opsview software repositories include the following packages in source form:

• opsview-external
• opsview-jasper
• opsview-monitoring-scripts-base
• opsview-netaudit-external
• opsview-perl-external
• opsview-python3-modules
• opsview-timeseries-influxdb
• opsview-watchdog

Opsview Agent End of Support

The opsview-agent source package, which included the Opsview Linux Agent, is no longer supported and is not available for download. Deploy all monitoring with the ITRS Infrastructure Agent.

Repository Version Copied

Before you download or build source packages, identify the repository version string that matches your Opsview release. You use this string later when you add the Opsview repository.

1. Determine your Opsview version:
   • If Opsview is already installed, check Configuration > My System in the UI.
   • If Opsview is not installed, use the latest version.
2. Look up the corresponding repository version string in the Release Notes.

For example, Opsview version 6.12.3 maps to the repository version string 6.12.3.202606301100.

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).

Building 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.

Support Policy

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

Debian Source Packages Copied

In the commands below, replace each instance of opsview-watchdog with the package name you are building.

Rebuilds

If a build fails (for example, due to missing dependencies), delete the current source tree and start again from the beginning to avoid file conflicts.

On a fresh Debian system, complete the following steps:

1. Update the package index and install the build tools:

   sudo apt-get update
   sudo apt-get install build-essential fakeroot devscripts debhelper
   

   • If you are building opsview-external, also run sudo apt-get install python2.7-dev.
   • If you are building opsview-jasper, also install JDK 11 and the JDK development tools.

2. Create a Python virtual environment at /opt/build-scripts/venv (this may require additional prerequisites):

   sudo python3 -m venv /opt/build-scripts/venv
   

3. Install pyyaml in that virtual environment.

4. Add the Opsview repository, replacing VERSION with the repository version from Repository Version:

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

5. Update the package index and install Opsview setup:

   sudo apt-get update
   sudo apt-get install opsview-setup
   

6. Edit /etc/apt/sources.list.d/opsview.list and change deb to deb-src so apt can access the sources repository.

7. Update the package index again:

   sudo apt-get update
   

8. As a non-root user, download and extract the source package into the current directory:

   apt-get source opsview-watchdog
   

9. Change to the extracted source directory:

   cd opsview-watchdog-*
   

10. Make any required modifications using standard Debian packaging practices.

11. Build the package:

    make package
    

    • Additional build-dependent packages may be required.

    • On Ubuntu, if /usr/bin/python2 is missing, create a symlink and continue the build:

      sudo ln -s /usr/bin/python2.7 /usr/bin/python2
      

12. After a successful build, locate the .deb file in the parent directory.

RPM Source Packages Copied

In the commands below, replace each instance of opsview-watchdog with the package name you are building.

Rebuilds

If a build fails (for example, due to missing dependencies), delete the current source tree and start again from the beginning to avoid file conflicts.

On a fresh RPM platform, complete the following steps:

1. Install the build tools:

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

   • If you are building opsview-external, also run sudo yum install python-devel (on RHEL 8/OL 8, use sudo yum install python2-devel).
   • If you are building opsview-jasper, also install JDK 11 and the JDK development tools.

2. Add the Opsview repository, replacing VERSION with the repository version from Repository Version:

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

3. Install Opsview setup:

   sudo yum install opsview-setup
   

4. Download the source RPM:

   yumdownloader --source opsview-watchdog
   

5. Make any required modifications using standard RPM packaging practices.

6. To build the source as-is, run:

   sudo rpmbuild --define "__arch_install_post /bin/true" --rebuild *.src.rpm
   

   Built RPMs are placed in /root/rpmbuild/RPMS/. The source location may differ if you make modifications.

   • Additional build-dependent packages may be required.
   • You may need to install EPEL for these dependencies.

Installing modified packages Copied

To install a package that you have built:

1. Install the package manually with the appropriate package manager on your Opsview system.
2. Rerun the setup-everything.yml playbook across the entire system.
3. Restart all components.

Support Notice

Packages built in this way are not covered by the Opsview support policy, even if the source is unmodified.

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

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 extract the source code for Opspack plugins and apply provided patches.

Setup Opsview Repositories Copied

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

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.

Installing modified plugins Copied

To install a modified plugin, import it under a new name by using the UI, API, or CLI.

Support Notice

Plugins built in this way are not covered by the Opsview support policy, even if the source is unmodified.

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, complete the following steps:

1. Update the package index and install the build tools:

   sudo apt-get update
   sudo apt-get install build-essential fakeroot devscripts debhelper
   

2. Add the Opsview repository, replacing VERSION with the repository version from Repository Version:

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

3. Edit /etc/apt/sources.list.d/opsview.list and change deb to deb-src so apt can access the sources repository.

4. Update the package index again:

   sudo apt-get update
   

5. As a non-root user, download and extract the source package into the current directory:

   apt-get source opsview-python3-modules
   

6. Change to the extracted source directory:

   cd opsview-python3-modules-*
   

   You can view the source code and patch files in this directory structure.

7. Apply all modifications:

   make patches-external
   

   Patched libraries are available as .tar.gz archives in build/index.

   Additional build-dependent packages may be required.

RPM system Copied

On a fresh RPM platform, complete the following steps:

1. Install the build tools:

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

2. Add the Opsview repository, replacing VERSION with the repository version from Repository Version:

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

3. Download the source RPM:

   yumdownloader --source opsview-python3-modules
   

4. Extract the source RPM contents, then extract the resulting archive:

   rpm2cpio opsview-python3-modules-*.src.rpm | cpio -id
   tar -xzf opsview-python3-modules-*.tar.gz
   

5. Change to the extracted source directory:

   cd opsview-python3-modules-*
   

   You can view the source code and patch files in this directory structure.

6. Apply all modifications:

   make patches-external
   

   Patched libraries are available as .tar.gz archives in build/index.

   Additional build-dependent packages may be required.