An Opspack is a configuration bundle consisting of a Host Templates with associated Service Checks, Plugins and Host Attributes that can be used to monitor a specific service or device with minimal extra configuration.
To get more details on the Opspacks included within Opsview Monitor, have a look at the Opspacks page on the main website.
Opspacks are no longer available to download from the opsview.com website. This is because newer Opspacks often rely on the most recent release of Opsview Monitor and are not backwards-compatible with earlier releases.
All Opspacks are automatically included in every release made, so in many cases you can upgrade to the latest available version of Opsview Monitor to get the update you are looking for.
In certain circumstances, if the Opspack you are looking for is not present and you are using the latest version, then it is likely that this will be available in the next major release - if you wish to check this, please raise a support incident to verify with us through the ITRS Support website.
You can also write your own plugins, see Active Checks for more information.
You may wish to easily exchange a Host Template with another Opsview Monitor instance. This section will show you how to export an Opspack from the Host Templates page. For more information, see Host Templates - Exporting/Importing Opspacks.
To use the AWS service checks, they only require user access via the Cloudwatch API and therefore no specific security group requirement exist, apart from the user would require read only access and/or belong to the group which allows API access.
Opspacks may be updated and released for newer versions of Opsview. You may check via the UI if you have that Opspack through the Host Templates page or via the command line. In order to check this via the command line and the version of that Opspack, you may use the below. This is to be run from your orchestrator server.
/opt/opsview/coreutils/utils/cx opsview "select name, version from opsview.monitor_packs order by name;"