Opsview 6.9.x Release Notes

Opsview 6.9.x End of Support

Opsview versions 6.9.x reached their End of Support (EOS) status at the end of January 2026, in accordance with our Support Policy. As of this date, these versions no longer receive code fixes, security updates, maintenance releases, or backported changes.

The documentation for version 6.9.7 and earlier releases will remain accessible for reference, but it will no longer be updated or maintained. We strongly recommend upgrading to the latest supported version of Opsview to ensure continued support and access to the latest features and security enhancements.

For release notes for Opsview 6.10.x and later versions, please refer to the Opsview 6.x Release Notes.

Opsview 6.9.7 Copied

Released: 26 February 2025

Highlights Copied

These are the highlights of this release:

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-71820 Fixed an issue that caused remotely managed cluster upgrades to fail when the cluster names contained opsview cluster or opsview_cluster (case-insensitive). The failure was due to messagequeue user permission errors. Now, the upgrade process and the collectors’ messagequeues operate successfully. For more information, see Additional upgrade steps.

Note

The additional upgrade steps for Opsview versions between 6.9.2 and 6.9.6 to 6.9.7 or newer must only be performed if your cluster names contain those strings; otherwise, you can proceed with the standard upgrade process.

Opsview 6.9.6 Copied

Released: 30 October 2024

Highlights Copied

These are the highlights of this release:

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-42988

Escaping of macro delimiter characters ($) is no longer required in arguments, strings, and variables. If a macro string is invalid, it will be kept unchanged in argument strings for event handlers, notification scripts, and plugins.

For backward compatibility, a pair of delimiter characters ($$) will be replaced with a single $, but this behavior will be removed in a future version. To prevent future compatibility problems, please replace all instances of $$ with $ in your configuration.
OP-70587 Fixed an issue where old messages missing agent configuration could cause the scheduler to fail. Additionally, fixed EPEL repository setup on CentOS 7, OEL 7, and RHEL 7 collectors.

Opsview 6.9.5 Copied

Released: 26 June 2024

Highlights Copied

These are the highlights of this release:

Known issue

There is a known issue affecting Opsview version 6.9.3 and 6.9.4 if brand new non-remotely managed monitoring clusters or collectors are deployed. This could result in loss of monitoring functionality across the clusters using the new servers.

If you deployed brand new non-remotely managed clusters or collectors using Opsview version 6.9.3 or 6.9.4, run the utility playbook with the following command: /opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/datastore-check-clustering.yml. Please contact ITRS Support for resolution steps if instructed.

Non-remotely managed clusters and collectors can be deployed correctly using Opsview version 6.9.5.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-68082 Fixed an issue where newly deployed non-remotely managed collectors or clusters would not form Opsview Datastore clusters correctly.

Opsview 6.9.4 Copied

Released: 11 June 2024

Highlights Copied

These are the highlights of this release:

Known Issue

There is a known issue affecting Opsview version 6.9.3 and 6.9.4 if brand new non-remotely managed monitoring clusters or collectors are deployed. This could result in loss of monitoring functionality across the clusters using the new servers.

If you have already deployed brand new non-remotely managed clusters or collectors using Opsview version 6.9.3 or 6.9.4, run our utility playbook using /opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/datastore-check-clustering.yml and contact ITRS Support for resolution steps if directed.

You should upgrade to Opsview version 6.9.5 before attempting to deploy new non-remotely managed monitoring clusters or collectors.

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-36830 Implemented checks to identify hostnames containing uppercase characters, since these can lead to configuration problems with message queues. Opsview deployments do not support uppercase characters in short hostnames or the FQDN (Fully Qualified Domain Name) of the systems. For more information, see the Collector prerequisites and Hostname documentation.
OP-51929 Opsview Deploy example files are now in line with the Supported databases policy.
OP-62989 Added option to set the memory high watermark for each message queue through Opsview Deploy.
OP-63424 You can now delete individual remotely managed collectors directly from the UI. See the Collector Management page.
OP-65135 Updated the installation of the Opsview repository GPG keys on Ubuntu systems due to security improvements and the deprecation of apt-key.
OP-66817 Python-based Opsview components now include their process ID when logging messages to the syslog.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-39831 Fixed an issue in the downtime manager where downtimes submitted for different objects at the same time were incorrectly treated as duplicates.
OP-63411 Fixed an issue in the database TLS configuration which resulted in deployment failures.
OP-65415 Fixed database connection issues encountered when running plugins in Opsview. Previously, when running plugins in Opsview that utilized DBD::mysql for database connections, a warning message WARNING: MYSQL_OPT_RECONNECT might be logged to standard error (stderr).
OP-66431 Reduced the likelihood of invalid downtimes appearing in the UI during prolonged cluster offline periods.
OP-67342 Updated the MySQL library requirements for Opsview plugins on RHEL8/OL8 and RHEL9/OL9 to prevent library loading problems.
OP-67374 Updated the version of Spreadsheet-ParseExcel used to address a security vulnerability.

Opsview 6.9.3 Copied

Released: 15 May 2024

Note

This release includes all the features from 6.9.2 that were withdrawn due to upgrade issues which have now been fully resolved. We also recommend reviewing the 6.9.2 release notes, especially the known issues related to the remote collector enhancements.

Highlights Copied

These are the highlights of this release:

Known Issue

There is a known issue affecting Opsview version 6.9.3 and 6.9.4 if brand new non-remotely managed monitoring clusters or collectors are deployed. This could result in loss of monitoring functionality across the clusters using the new servers.

If you have already deployed brand new non-remotely managed clusters or collectors using Opsview version 6.9.3 or 6.9.4, run our utility playbook using /opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/datastore-check-clustering.yml and contact ITRS Support for resolution steps if directed.

You should upgrade to Opsview version 6.9.5 before attempting to deploy new non-remotely managed monitoring clusters or collectors.

Note

Upgrading from Opsview 6.9.2 might leave a reference to the opsview_orchestrator_mq user in your /opt/opsview/deploy/etc/user_secrets.yml file. You can safely remove it manually.

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-36830 Implemented pre-deploy checks to identify hostnames containing uppercase characters, which can lead to configuration problems with message queues. Opsview deployments do not support uppercase characters in short hostnames or the FQDN (Fully Qualified Domain Name) of the systems.
OP-58195 Added search functionality to the plugin drop-down menu for creating new service checks and selecting plugins.
OP-58578 Fixed an issue in Opsview Watchdog that caused Skipping 'allow localhost' warnings to appear during fresh installations and upgrades.
OP-63425 You can now delete all remotely managed collectors using the API. For more information, see Remote Collector Management.
OP-63931 You can now delete remotely managed collector clusters from the Collector Management page.
OP-64520 The Downtime column within the Host Group List dashlet now shows a tooltip for Downtime status.
OP-65136 Added an option to ignore missing interface speed or ifSpeed within the check_snmp_interfaces_cascade plugin (new --ignore-no-speed option). This allows interfaces to be shown with OK status even if their ifSpeed is 0.
OP-66039 Fixed a compatibility issue with the php-fpm library, in preparation for future OS support.
OP-66692 Updated opsview-watchdog to synchronize the monitor daemon frequency with the deploy configuration.
OP-66707 Display Downtime Invalid message in the Investigate windows when an inconsistency in the downtime state is detected.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-41955 If Rancid was not properly configured, the run_rancid_collect script no longer emits an error, and exits with exit code 0. This prevents sending unnecessary Opsview emails due to unconfigured Rancid.
OP-48975 The setup-monitoring playbook now successfully establishes the intended session, resolving the previous banner-related errors.
OP-49377 Pressing the Enter key while a host is selected in the Host Search drop-down menu now directly clicks on that entry, streamlining the process of choosing your desired host.
OP-62909 When the opsview_collector_allow_disconnected option is in use, scheduler now resumes normal function after prolonged disconnection from the orchestrator via SSH tunnel and direct connection.
OP-64129 Fixed an issue with the Query Host function when using SNMP GetNext. The POST request now utilizes the GetNext method within its payload.
OP-64569 Fixed issues that caused validation error messages to display when setting up downtime in the BSM dashlets.
OP-64570 Fixed the following issues affecting BSM:
  • Tooltips for grid columns within the Host Group List dashlet now display accurate information.
  • Corrected Downtime icon to reflect downtime status within the Host Group List dashlet.
  • Downtime validation is now consistent when initiated through BSM dashlets.
  • Downtime comment prefixes are now consistent across different BSM object types.
OP-65417 Oracle Linux 9 (OL 9) is now a supported operating system for Opsview Monitor and Opsview Collectors.
OP-65465 Fixed an issue in the Collector Management UI where all collectors were mistakenly identified as the last collector in a cluster, preventing their deletion.
OP-65841 Fixed an issue in the Agent client that prevented it from communicating with a host using anonymous ciphers on CentOS/RHEL/OEL 7.
OP-65957 Fixed an issue with SNMP configuration in opsview-deploy that prevented it from accommodating listening on IPv6 in addition to IPv4, and caused it to use an incorrect MIB subtree.
OP-66069 Fixed issues encountered when adding opsview-datastore nodes during registration of new collectors with existing clusters.
OP-66159 The remote collector bootstrap script now creates a backup of existing user_secrets with a filename that deploy does not read as config.
OP-66198 Fixed an issue encountered during upgrades of the opsview-watchdog package. Previously, errors related to monitrc file permissions might not have been logged.
OP-66202 Collection plans using Agent commands (check_nrpe) created by 6.9.3 orchestrators are now compatible with 6.9.1 collectors.
OP-66441 Fixed issues associated with deleting clusters (locally and remotely managed) via the UI and the dataserver API.
OP-66549 Fixed an issue during Opsview 6.9.2 upgrades that prevented creation of new MQ users and permissions if the machine reference contained a newline character.
OP-66686 Enhanced error messaging during reloads that fail due to agent checks passing unknown arguments to the check_nrpe client.
OP-66687 The new agent client now supports the -u flag.
OP-66773 Fixed an issue that prevented loading the crypto library (opsview-datastore) in preparation for future OS support.
OP-66827 Improved the SNMP functionality to ensure proper agent address reporting. Previously, SNMP changes for the agentAddress field only worked if both IPv4 and IPv6 addresses were configured on the loopback device.
OP-66831 Fixed an issue where playbooks used for system configuration were missing the opsview_machine_ref attribute.

Opsview 6.9.2 Copied

Released: 9 April 2024

Opsview 6.9.2 Release Withdrawn

Withdraw of the 6.9.2 Release

Unfortunately, due to critical issues identified with version 6.9.2, we have decided to remove it and ensure it’s no longer available for download. These issues impacted the ability to install or upgrade, but none were security-related.

We are diligently working to resolve these issues and are planning to release an updated version 6.9.3 in early May.

What if you’ve already upgraded

For customers who have already upgraded to 6.9.2, no immediate action is required, as none of these issues are security-related. Once it’s available, you will still be able to upgrade to 6.9.3 as normal.

We appreciate your patience and trust as we continue to enhance our software to better serve you. Thank you for your understanding.

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the new features and enhancements of this release:

Issue key Description
OP-60300 Opsview Monitor on RHEL 9 supports monitoring your hosts running on both the Infrastructure Agent and the legacy Opsview Agent. This allows you to check the state of your servers consistently with how Opsview deployments functioned in previous RHEL versions.
OP-64790 The following third-party components were upgraded: RabbitMQ 3.12.12, CouchDB 3.3.3, Erlang 25.3.2.9, SpiderMonkey 78.15.0 and 91.13.0, to allow additional OS support.

Note

Due to a significant update to the messagequeue library, upgrading collectors to this version of Opsview or higher will remove all unprocessed messages from the message queues. This is expected behavior and will not affect functionality after the upgrade.
OP-64798 RHEL 9 (Red Hat Enterprise Linux 9) is now a supported operating system for Opsview Monitor, Opsview Collectors, and the Infrastructure Agent. OL 9 (Oracle Linux 9) is now a supported operating system for the Infrastructure Agent.
OP-64801 Hashtags can now apply to individual monitored objects to complement the existing bulk tagging. This allows more fine-grained configuration of hashtags, such as adding checks from a single host interface to a hashtag. For more information, see Adding a Hashtag.
OP-64422 Notification methods for BSM services and components can now be run on clusters other than the Master Monitoring Collector. The collector cluster to use for a BSM service or component can be selected from the BSM configuration screens. This allows custom notification methods to be used on customer-owned collector clusters in Opsview. For more information, see Create Business Components and Services.
OP-65401 Each non-remotely managed collector and its associated monitoring host is automatically deleted when the non-remotely managed cluster is deleted. For more information, see Managing clusters and collectors.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-54364 The monit daemon shutdown script now ensures all Opsview services are properly stopped before initiating a server reboot. This prevents potential data corruption or service disruptions during the reboot process.
OP-56573 Updated Opspack: Cloud - Azure (v2.3.1). Fixed an issue where certain Azure service checks were failing due to limitations in handling timestamp precision. Now, Azure checks can process input timestamps with microsecond precision regardless of the time zone. However, it’s important to note that for optimal functionality, it’s recommended to consistently use timestamps in UTC whenever possible.
OP-59076 Fixed an issue that caused day labels to be missing occasionally on timeseries graphs. Now, date labels are consistently displayed on the x-axis between 1 and 7 days range.
OP-60506 The setup-opsview YAML file now accepts any valid characters for the database password. Previously, using the # character in the password caused the deployment to fail.
OP-61129 Upgraded Samba version used by the WMI within opsview-external to address security vulnerabilities. The check_wmi_plus plugin is now written in Python and not taken from third party sources. Also, the following Opspacks have been updated to use the new plugin:
  • Application - Microsoft Hyper-V Agentless (v3.0.0)
  • OS - Windows WMI - Base Agentless (v.3.0.0)
  • OS - Windows WMI - DNS Agentless (v.3.0.0)
  • OS - Windows WMI - IIS Server Agentless (v3.0.0)
  • OS - Windows WMI - Terminal Services Agentless (v3.0.0)
  • OS - WMI Client (v3.0.0)
OP-61684 Addressed MQ vulnerabilities using remote collectors in Opsview. Also, the read and write messages have been disabled from/to the orchestrator queues to prevent potential malicious users from sending messages from a remote collector pretending to be the orchestrator.
OP-64257 Updated Opspack: Application - Uptrends (v1.0.3). Opspack now uses the latest Uptrends API to ensure that all checks work correctly.
OP-64437 Fixed an issue where performing multiple reloads with backed-up results messages could cause deadlocks, slowing down the reload process.
OP-65478 The check_deploy script can now validate database passwords even when testing with remotely managed collectors. This fixed a previous issue where the script failed due to a variable only being accessible within the orchestrator itself.
OP-65530 Fixed an issue where remote collectors would disconnect from the orchestrator if the orchestrator’s IP address changed.
OP-65621 The new agent client now works with both Windows and Linux versions of the legacy Opsview Agent.
OP-65815 The opsview-messagequeue component setup has been made more reliable during deployment of multi-collector clusters.
OP-65822 The opsview-datastore component setup has been made more reliable during deployment of multi-collector clusters.
OP-65888 Fixed an issue where collectors were getting permission denied when trying to write to the collector queue (collector-queue_<orch-machine-ref>) and Results Live queues (results-live_<machine-refs>).
OP-66132 The opsview-sshtunnels component now correctly cleans up child processes on shutdown or restart.

Opsview 6.9.1 Copied

Released: 28 February 2024

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the new features and enhancements of this release:

Issue key Description
OP-42202 The following Opspacks have been updated:
  • Cloud - Azure - Internet of Things (v2.1.3) — Updated plugin to support new Azure libraries.
  • Cloud - Azure - Generic (v.2.0.4) — Updated plugin to support new Azure libraries.
  • Cloud - Azure (v.2.3.0) — The “Cloud - Azure - Network Watcher - Connection Monitors” Host Template is now available, while the “Cloud - Azure - Network Watcher - Classic Connection Monitors” Host Template has been deprecated.
OP-63423 The version of Nginx used within Opsview has been updated in preparation for future OS support.
OP-64224 You can now export the NetFlow Sources History graph to the following file types: png, jpeg, pdf, svg, xlsx, csv, and json.
OP-64363 To ensure compliance, all copyright references to 2023 have been changed to 2024.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-63547 Opsview repository GPG key updated for future OS support.
OP-64233 The package information in Opsview has been updated to ensure it is up-to-date.
OP-64518 Fixed an error where remotely managed clusters would become unavailable when the primary collector went offline. As a result of this fix, monitoring continues after any collector within the cluster goes offline, as long as at least one collector remains online.
OP-64616 The Collector Management page now shows a specific error message when deleting a cluster that monitors hosts.
OP-64902 The GPG key for the MySQL 8.0 repository has been updated. Since MySQL 5.5 and 5.7 are no longer supported (EOL), we recommend upgrading to MySQL 8.0 for continued support and security updates.
OP-64911 Fixed an issue that caused the remote collector setup to specify an incorrect IP address for the orchestrator in the /etc/hosts file.
OP-65159 Fixed an issue where the plugin migration check could fail after encountering an error during deployment.

Opsview 6.9.0 Copied

Released: 24 January 2024

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the new features and enhancements of this release:

Issue key Description
OP-62096 The Monitoring Plugins UI now shows if a plugin is user-uploaded or built-in. In addition, both the UI and the /rest/config/plugin API endpoint now prevent deletion of built-in plugins, or any plugins in use.
OP-62097 Monitoring scripts (including plugins, event handlers, and notifications) and their configuration files are now deployed along with other changes during Apply Changes:
  • Remote Collectors can now run service checks using user-uploaded plugins correctly.
  • The sync_monitoringscripts playbook has been removed.
  • To understand which systems get updated with specific uploaded files during the Apply Changes process, see Apply configuration changes. It also explains the process limitations, including the maximum data size allowed or can be sent before it fails.
  • The /opt/opsview/monitoringscripts/etc/notificationmethodvariables.cfg file on each collector has been moved to /opt/opsview/monitoringscripts/var/notifications/notificationmethodvariables.cfg.
  • The /opt/opsview/monitoringscripts/etc/plugins/check_snmp_interfaces_cascade directory on each collector has been moved to /opt/opsview/monitoringscripts/var/plugins/check_snmp_interfaces_cascade/.
  • The UI now shows if uploaded monitoring plugins have empty help text.
  • The Audit Log now records a RELOAD entry with the error details for any failed Apply Changes operation.
  • Monitoring scripts (including plugins, event handlers, and notifications) and their configuration files are now deployed along with other changes during Apply Changes.
The following Opspacks have been updated to use consistent help text behavior in plugins and work with script distribution:
  • Application - Alfresco (v2.1.1)
  • Application - Jenkins (v2.0.2)
  • Application - Microsoft DNS Agentless (v2.2.1)
  • Application - Microsoft Hyper-V Agentless (v2.2.5)
  • Application - Microsoft Hyper-V Server Agentless (v2.2.2)
  • Application - Microsoft IIS Agentless (v2.2.2)
  • Application - Microsoft Message Queue Agentless (v2.2.2)
  • Application - Opsview (v3.1.1)
  • Application - Varnish Cache 3.0 (v2.1.1)
  • Application - Varnish Cache (v2.1.1)
  • Cloud - Azure - Generic (v2.0.3)
  • Cloud - Azure - Internet of Things (v2.1.2)
  • Database - Microsoft SQL Database States Agentless (v2.2.2)
  • Database - Microsoft SQL Performance Agentless (v2.2.2)
  • Database - Microsoft SQL System Agentless (v2.2.2)
  • Database - Microsoft SQL (v2.1.2)
  • Database - MongoDB (v2.1.3)
  • Database - MySQL Server (v2.2.1)
  • Database - Oracle RDBMS (v2.0.2)
  • Database - PostgreSQL (v2.0.3)
  • Export - Capacity Planner (v1.1.1)
  • Infrastructure - Netbotz (v2.0.2)
  • Network - Linksys Wireless (v2.0.2)
  • Network Services - LDAP (v2.0.1)
  • Network Services - TFTP (v2.0.1)
  • Opsview - Sync LDAP (v1.0.1)
  • OS - Linux SNMP (v2.0.4)
  • OS - Microsoft Exchange Counters (v2.0.2)
  • OS - Microsoft Exchange 2013 back pressure (v2.0.2)
  • OS - Microsoft Exchange 2016 back pressure (v2.0.2)
  • OS - Unix Agentless (v2.0.2)
  • OS - Windows Base Agentless (v2.3.1)
  • OS - Unix Agentless (v2.0.2)
  • OS - Windows Base Agentless (v2.3.1)
  • OS - WinRM Agentless (v2.3.2)
  • OS - Windows WMI - Base Agentless (v2.1.5)
  • OS - Windows WMI - DNS Agentless (v2.1.5)
  • OS - Windows WMI - IIS Server Agentless (v2.1.5)
  • OS - Windows WMI - Terminal Services Agentless (v2.1.5)
  • Service Provider - AQL (v2.0.1)
  • Service Provider - Slicehost (v2.0.1)
  • SNMP - MIB-II (v4.1.1)
OP-63899 Deleting entire remotely managed clusters is now possible through the API, accessible only to authorized users. Upon deletion, both the cluster and its collectors are removed from the database, and the collectors’ public SSH keys are purged from the orchestrator. However, this functionality is limited to remotely managed clusters; non-remotely managed clusters and collectors cannot be deleted through the API.
OP-63915 Administrators of remotely managed clusters can now initiate complete cluster deletion directly from the collector command line. This process utilizes the dataserver API and requires user authentication through the REST API, ensuring secure access.
OP-64125 This release introduces some changes that may affect existing configurations:
  • The envvars database column in the opsview.plugins table is no longer used.
  • # OPSVIEW BEGIN INFO, # Macros: comments in plugins are no longer used.
  • The check_nagios_startup plugin has been removed due to compatibility issues.
  • Future releases of these plugins will offer command-line options, replacing the current environment variables approach: check_mysql_performance, check_opsview_mysql_performance, check_snmp_interfaces_cascade, check_snmp_linkstatus, and check_snmp_tcpcurrestab_cssfix.
  • The current behavior of passing environment variables to notification scripts and event handlers remains unchanged.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-59380 An issue in the ServiceNow notification method preventing tickets from being closed has been resolved. This was caused by ServiceNow REST API changes. Local database entries are now always removed on ticket closure, regardless of external communication success. Additionally, retries have been added to address temporary gateway problems and connection issues to ServiceNow. If you’re still using the old ServiceNow REST API, you can revert to the previous behavior using a custom configuration YAML file. Details on this process are available in ServiceNow notifications.
OP-64349 Fixed an issue in check_jmx that caused incorrect argument handling, leading to errors like JMX UNKNOWN Required options not specified Usage: check_jmx -help.
OP-64449 An issue on non-cloud systems flagged up an invalid /opt/opsview/monitoringscripts/opspacks-beta/': No such file or directory error. This has now been removed.
OP-64498 Updated Opspack: OS - Unix Advanced (v2.2.0). A fix has been implemented to resolve missing NRPE certificate arguments in the “Total files in /var/log” service check.

Disclaimer

The information contained in this document is for general information and guidance on our products, services, and other matters. It is only for information purposes and is not intended as advice which should be relied upon. We try to ensure that the content of this document is accurate and up-to-date, but this cannot be guaranteed. Changes may be made to our products, services, and other matters which are not noted or recorded herein. All liability for loss and damage arising from reliance on this document is excluded (except where death or personal injury arises from our negligence or loss or damage arises from any fraud on our part).
["Opsview On-Premises"] ["Release Notes"] "1"

Was this topic helpful?