Opsview 6.x Release Notes

Overview Copied

Opsview release notes contain the list of enhancements of features, and a set of issues fixed in the currently supported versions of Opsview Monitor. Note that any fixes from previous release dates are rolled up into the latest release. For more information, see Support Policy.

Before you install Opsview, make sure to check the 6.x Compatibility Matrix. For details on installation, administration, and usage, you may refer to Opsview Monitor documentation. For the latest highlights, see What’s New in Opsview.

For Opsview 6.8.x release notes, you can access them at Opsview 6.8.x Release Notes. For Opsview 6.7.x and older release notes, refer to the Opsview Knowledge Center.

Opsview 6.11.2 Copied

Released: 21 May 2025

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-54491 Opsview now supports the following SNMPv3 authentication protocol options:
  • sha224 (SHA-224)
  • sha256 (SHA-256)
  • sha384 (SHA-384)
  • sha512 (SHA-512)
For more information, see Supported SNMPv3 Protocols.
OP-73297 The id field in the opsview.auditlogs table has been updated from int to unsigned int, doubling its maximum value. This addresses the risk of the audit log id reaching its previous limit due to frequent passive check submissions via the REST API. For high-frequency checks, we recommended using the Results Forwarder to help avoid inflating audit log entries.
OP-73579 Added new monitoring with cluster health alarm for messagequeue issues such as network partitions and memory throttling on the orchestrator. The Configuration > Collector Management page has been updated to show these issues in tooltips, helping you track the health of your master RabbitMQ cluster even if the standard self-monitoring checks are not running. For more information, see Cluster Health Alarms.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-37229 Opsview can now handle cleanup tasks for flow collector data using a scheduled cron job. Previously, netflow data had no defined retention period, which caused the file system to become full. For more information, see Flow collector housekeeping.
OP-43922 The housekeeping job for the runtime database now works successfully regardless of the number of messages being processed by results-live and results-recent.
OP-57486 Fixed an issue where service checks were immediately marked as stale upon entering their scheduled check period following a monitoring suspension. The Freshness Checker has been updated to include a check interval to the freshness timeout, preventing false alerts by allowing checks sufficient time to run before being evaluated for staleness. For more information, see Freshness Checking.
OP-63516 Deleted documents in the opsview-logs and opsview-sessionmanager databases can now be automatically removed from the system, improving database performance and efficiency.
OP-73132 Fixed a race condition where Apply Changes failed if the system attempted to stop a task that had already completed.
OP-73133 Fixed argument parsing issues in check_dns. Now, the plugin works successfully using standard input (stdin) or command line arguments.
OP-73646 Fixed an issue where uploaded notification scripts could fail to run when executed during metadata file creation.
OP-73735 Fixed performance issues in the configuration windows of the following dashlets:
  • Performance Graph
  • Performance Gauge
  • Metric Pie Chart
  • Process Map
  • Top Services by Metric
This results in faster load times and improved responsiveness on dashlets when selecting hosts, service checks, and metrics in large-scale systems. For more information, see Dashlets.
OP-73820 The executor agent client (the current built-in check_nrpe plugin) has been updated to function similarly to the check_nrpe plugin from Opsview versions prior to 6.9.2. Previously, when a connection to the agent was refused, an UNKNOWN was returned. Now, the plugin returns a CRITICAL status. The new --unknown-connection-refused plugin option is available to return UNKNOWN in these situations instead; this only works once the whole system, including collectors, has been upgraded.
OP-73833 Fixed an issue in the opsview.reload_stages table where the current_stage value could exceed the max_stages value, which resulted to a disproportionate progress in the reload bar.

Opsview 6.11.1 Copied

Released: 3 April 2025

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-73311 Results Exporter has been updated to use ITRS Analytics version 2.x APIs. As a result, the following versions of the ITRS Analytics Platform are now compatible with Dynamic Thresholds in Opsview:
  • Platform version 2.6.1
  • Platform version 2.7.0
  • Platform version 2.8.0
For more information, see Dynamic Thresholds compatibility matrix.
OP-72846 References to obcerv in the Dynamic Thresholds and Results Exporter documentation have been updated to use analytics for configuration. We recommend updating your configuration to prevent component issues in the future. For more information, see Configuring Dynamic Thresholds.
OP-72236 MariaDB 10.11 is now supported as the non-default database option for Opsview deployments on Ubuntu 20 and 22. For more information, see Supported databases.
OP-72235 MariaDB 10.11 is now supported as the default database in Opsview for RHEL 9.4 and OL 9. For more information, see Supported databases.
OP-72234 MariaDB 10.11 is now supported as the default database in Opsview for RHEL 8.10 and OL 8. For more information, see Supported databases.
OP-72149 The opsviewd component has been removed from Opsview Monitor. Its functionality has been re-implemented in the Orchestrator’s REST API.
OP-71025

The check_wmi_plus.pl Perl plugin has been deprecated. If you are using this plugin, we strongly recommend updating your service checks to use the check_wmi_plus Python plugin for improved security.

The following Opsview-provided Opspacks might be affected if the system has been deployed before Opsview version 6.9.2:

  • OS - Windows WMI - Terminal Services Agentless Opspack
  • OS - Windows WMI - IIS Server Agentless Opspack
  • OS - Windows WMI - DNS Agentless Opspack
  • OS - Windows WMI - Base Agentless Opspack
  • Application - Microsoft Hyper-V Agentless Opspack

The check-deploy playbook will identify and list all affected service checks for manual updates. Once updated, all service checks will continue to work as expected.
OP-61973

Automatically deployed self-monitoring hosts in Opsview now monitor two new checks against opsview-messagequeue nodes:

  • Opsview - MessageQueue - Partitions
  • Opsview - MessageQueue - Memory Usage Watermark

These use two new modes of the built-in check_rabbitmq_node plugin:

  • partitions — detects if a node is aware of a cluster network partition and the other nodes that are separated.
  • mem_usage_watermark — returns memory usage as a percentage of the configured memory watermark limit and outputs the limit itself.
For more information, see MessageQueue.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-73168 JasperServer’s Spring and Tomcat libraries have been updated to address security vulnerabilities. For more information, see Reporting Module.
OP-72417 The check_wmi_plus plugin now displays the correct help text in the Plugin Help.
OP-70516

When configured to export data to ITRS Analytics, Results Exporter now detects and reports data that violates constraints in ITRS Analytics before sending it. This helps prevent silent data loss.

Additionally, the truncate field operation is now available in Results Exporter outputs to enforce a maximum length on exported string custom fields. For more information, see Exporting Results.
OP-64283 Fixed an issue when using an SSO provider with Opsview, alongside configured alternative webserver addresses. Now, alternative addresses correctly support the sign-on functionality.
OP-63072 Go Language has been upgraded from 1.19.3 to 1.23.5 to address security vulnerabilities. For more details, see Software Components.
OP-44366 Fixed an issue in the Database - Microsoft SQL Opspack where a misspelling appeared in the Microsoft SQL - Active Transactions service check.
OP-61973 Cluster Health alarms for degraded clusters are now correctly shown in tooltips on the Configuration > Collector Management page. For more information, see Cluster Health Alarms.

Opsview 6.11.0 Copied

Released: 26 February 2025

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-71682 The Status Objects tab has been updated to use an itemselector for adding and removing host groups, service groups, and hashtags when editing roles. This allows efficient selection of items displayed in a list format with search functionality for quick filtering of items. For more information, see Status Objects.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-55269 Fixed an issue where AutoMonitor could not create host and host group names containing invalid characters. Invalid characters are now automatically removed before the names are imported into Opsview. The sanitized names are displayed in the scan logs.
OP-59714 NGINX has been upgraded to resolve security issues with third-party software. For more details, see Web Server Software.
OP-69151 The activemq-client library has been upgraded from 5.16.6 to 5.16.7 to address a security vulnerability. For more details, see Reporting Module.
OP-70400 The Kubernetes and OAuthlib libraries have been upgraded to resolve multiple service checks failing for Azure Kubernetes Pods. For more details, see Python Libraries.
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.

OP-72068 The ITRS Opsview Mobile App is back on Google Play after temporary unavailability. You can now install or update the app directly from the Play Store.
OP-72083 Opspack: OS - VMware vSphere (v3.0.1) has been updated to support the monitoring of clusters and datastores with names containing spaces via vCenter v7 and v8.
OP-72188 The pyopsview REST API client can now be used with multiple active connections to Opsview simultaneously.
OP-72369 Fixed an issue where Debian and Ubuntu systems could not sync plugins due to errors in rsync packages that caused checks to fail after a reload.
OP-72963 The check_wmi_plus plugin can now handle empty results when using the -4 option.
OP-73110 Fixed an issue in the Reporting Module where deleted host entries incorrectly appeared in reports filtered by a hashtag. Now, hashtag filters are passed through via sub-reports. This ensures that they are correctly applied to the entire final report.

Opsview 6.10.6 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.10.5 Copied

Released: 28 January 2025

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-64026 When enabled, the Opsview - Updates survey now collects and reports your MySQL version and vendor information. This data enables Opsview to prioritize future database changes more effectively.
OP-66050 For SNMP-enabled hosts, Ignore has been added as an available interface alert type. For more information, see Alert Type.
OP-69139 Opsview now supports Secure Arguments (also known as Secure Args) to improve the security of plugins, notification scripts, and event handlers by passing arguments via standard input (stdin) instead of the command line.
OP-70586 Multiple host variables can now be removed simultaneously via bulk selection. For more information, see Hosts.
OP-70669 You can now set the execution style of uploaded plugins, notification scripts, and event handlers to use Secure Args for argument passing. This is the recommended approach for enhanced security. For more information, see Secure Arguments.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-69153 Objects selected using Hashtag Individual Tagging and Interface Tagging for users with VIEWSOME now correctly display in the Navigator and send out notifications. For more details, see Adding a Hashtag.
OP-69614 MessageQueue permissions have been updated to resolve issues with NetAudit backups on clustered systems.
OP-70401 Fixed an issue where system downtime caused invalid stale results, which can wipe non-sticky acknowledgments on problem states.
OP-71571 Opsview cronjobs can now handle systems where /opt/opsview/coreutils/var/backups uses a symlink to another drive.
OP-71733 Fixed parsing issues in the check_wmi_plus plugin.

Previously, range parsing in thresholds was incorrect. Additionally, the checkeventlog mode had several limitations:

  • The -4 option was not recognized.
  • The -3 option did not support floating-point values.
  • An error occurred when the -o option’s argument began with a comma.
OP-71766 The opsview-python3-modules package now correctly depends on libyaml for the appropriate OS.
OP-72188 The pyopsview library provided in opsview-python3-modules has been upgraded to v6.2.5 to support multiple simultaneous connections. For more details, see pyopsview.

Opsview 6.10.4 Copied

Released: 11 December 2024

Highlights Copied

These are the highlights of this release:

Known Issue

For the Opsview Mobile App login, you must use the https://legacy.opsview.com site to manage your account as there are errors currently affecting user registrations. For more details, see Opsview 6.x Known Issues.

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-53802 SNMP-enabled hosts now use the ifName field by default during interface querying. For more information, see Use SNMP ifName.
OP-54915 The NetAudit UI has been updated to show hosts based on the permissions of the user. Ensure that you have the necessary permissions to view hosts. For more information, see NetAudit Troubleshooting.
OP-60756 AutoMonitor and Autodiscovery apps now have their own access controls (AUTOMONITOR and AUTODISCOVERY), separate from the CONFIGUREHOSTS access for the Hosts List page. This provides more granular permission options. During the upgrade, any Roles with CONFIGUREHOSTS will automatically gain AUTOMONITOR and AUTODISCOVERY permissions to maintain behavior. Additionally, a security update has been implemented to prevent unauthorized changes. As a result, AutoMonitor now requires both CONFIGURESAVE and AUTOMONITOR permissions.

Warning

If you previously relied on a role with CONFIGUREHOSTS but no CONFIGURESAVE to use AutoMonitor, this will no longer work.
For systems using multi-tenancy, any primary or tenant roles with unauthorized access will lose those privileges during this upgrade.
OP-62629 Opspack: OS - VMware vSphere (v2.1.0) has been updated. Opsview now supports vSphere 8 and vCenter 8.0 environments; the older versions of vSphere including 6.0, 6.7, and 7.0 continue to be supported, along with vCenter 6.7 and 7.0.
OP-67906 For the Opsview UI, Angular has been upgraded from v12 to v17 to resolve security issues with third-party libraries. For more details, see NodeJS Modules.
OP-70306 MySQL 8.0 is now supported as a non-default database choice for Opsview deployments on RHEL 9 and OL 9. See Supported Databases.
OP-70347 Dynamic Thresholds for Opsview Enterprise have been updated to improve the calculation of threshold values and support hard limits. The threshold macros used in Dynamic Thresholds compatible with Service Checks have been changed from WARNINGGT and CRITICALGT to WARNINGDT and CRITICALDT. This macro rename means that custom checks using the old macros must be updated to continue working.
OP-70540 Dynamic Thresholds algorithm for Opsview Enterprise has been improved to better support large metric value drops, which reduces noise generated by these changes.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-43192 When the changelog is enabled, cancelling downtime or deleting an acknowledge will now require a changelog message.
OP-44293 Fixed an issue in the check_snmp_memutil plugin where hosts without swap memory returned an Illegal division by zero error. Now, the plugin handles gracefully the instances where the total swap space is 0 or the swap and real memory have no existing OIDs.
OP-52700 Opsview system SNMP configuration file permissions have been updated to allow read and write access only to the root user.
OP-61898 AutoMonitor vSphere Express Scan and the OS - VMware vSphere Opspack now correctly handle nested folders in vCenter datacenters.
OP-65414 When self-monitoring is being set up, disk partitions mounted to paths greater than 64 characters will not be included.
OP-69936 Cloud - Azure Opspack documentation has been updated to include setting up the Azure Monitor Agent. This replaces the Log Analytics Agent for Azure VM Monitoring, which is a prerequisite for some Host Templates.
OP-70031 Filtering by Host Group now works correctly for Event Graph and Event Table dashlets. Upon opening the configuration options of Event Graph and Event Table, an access denied box will no longer appear for users without the CONFIGUREVIEW permission.
OP-70150 Fixed an issue with downtime creation where a user with ADMINACCESS can set downtime on objects they cannot view. Now, downtime creation and deletion both correctly affect objects a user is authorized to access.
OP-70284 When there is a connection error in Nucleon RabbitMQ adapter used for opsview-messagequeue, the error logs now include the specific details of the connection error.
OP-70296 Additional positional arguments to the executor agent client (check_nrpe) are now correctly passed to agents, which allows you to continue using existing custom service checks that use additional positional arguments. This also fixes a behavior change from 6.9.2 when the original check_nrpe plugin was replaced.
OP-71369 Reporting Module has been updated to support additional OS Java versions to fix startup issues on RHEL 9 systems.
OP-71656 Fixed an issue for Opsview Enterprise where service checks that use Dynamic Thresholds fail on collectors that run older versions than the Orchestrator.
OP-71702 Fixed an issue where upgrading remotely managed collectors fail due to a missing message parameter if their starting version was too old.
OP-71717 Fixed an issue where applying Notification Profiles in particular orders lead to invalid opsview-scheduler notification states.

Opsview 6.10.3 Copied

Released: 30 October 2024

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-53646 Hashtags can now be assigned to SNMP interfaces on hosts and their service checks using the new Interface Tagging tab when creating or editing a hashtag.
OP-65602 Improved selection of hosts by allowing text search in the BSM > Components configuration screen.
OP-66456 When configuring new Business Services or Components, the Notify Via field now automatically pre-selects the first available cluster (the Master Monitoring Cluster).
OP-68053 Results Exporter now handles unsupported output types by reporting warnings through the logs.
OP-69593 You can now filter SNMP interfaces by extra text strings in the Interface name column when querying.

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-45379 Audit logs no longer display notification script arguments after testing notifications.
OP-60757 The full name field for users now supports apostrophes.
OP-65198 The check_apache_performance plugin now handles properly the cases where there are workers gracefully restarted.
OP-65678 Fixed an issue where the service tooltip on host in the Hashtag view displayed incorrectly.
OP-66065 Opsview menu logo customizations now persist across upgrades.
OP-66163 You can now correctly export Host Templates using plugins that are not in use by your hosts.
OP-67311 The downtime REST API endpoint now returns a 400 error when a scheduled time with an end date or start time more than a year from the current date is created. Previously, this downtime would not work correctly, but the API would not report an error.
OP-67495 Autodiscovery now truncates discovered hosts names to 64 characters to prevent import issues.

Opsview 6.10.2 Copied

Released: 25 September 2024

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-68362 The opsview-sys-master package has been renamed to opsview-sys. It now creates configuration files as part of the deploy role, instead of during package build.
OP-68381 Reduced the number of times the ansible-interpreter role needs to be run during deployment.
OP-68641 You can now use the negate functionality implemented within the executor so that you get a more efficient system without the need to invoke an external plugin.
OP-68839 Enhanced the deployment process by optimizing the use of ansible_managed to facilitate easier debugging of templated files.
OP-69261 Improvements to SNMP Monitoring:
  • Added the --ignore-strange-percent-values option to ignore results exceeding 100%.
  • Added support for interfaces without specified speeds.
  • Added support for big integer (bigint) values for the throughput.
OP-69976 Improved performance of ODW importing. Please note that a new index has been added to the ODW database, which may result in a longer upgrade time. The new Daily Performance Summarized Report is three times faster and uses six times less disk space on the database server than the previous Daily Performance Report.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-53178 The opsview-state-changes distribution system has been improved to prevent message duplication and loss.
OP-65941 Fixed an issue that prevented notifications from being sent when a service returned from a downtime period. Notifications are now sent as scheduled after the downtime ends.
OP-67259 Exceptions occurring in the opsview-common registry helper are now logged.
OP-67849 Upon launching the opsview-dataserver service, the system now records the initial registration of endpoints in both the opsview.log and syslog files.
OP-68574 Fixed an issue that prevented PKI from generating client certificates due to an incorrect FQDN on the collector.
OP-69263 Under standard opsview-deploy configurations, when nodes experience intermittent network disconnections and reconnections (due to firewall actions, not VM suspensions), the system’s partition handling mechanism functions as expected.
OP-69273 Fixed an an issue that prevented opsview-sys from starting due to corrupted encrypted configuration files.
OP-69740 Fixed an issue that prevented the messagequeue node from joining the cluster when adding remote collectors.
OP-69779 Fixed Opsview mobile push notification issues.

Opsview 6.10.1 Copied

Released: 21 August 2024

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-65613 NetAudit now allows bulk password resets for multiple hosts.
OP-67475 Opsview and Infrastructure Agent can now be deployed on Ubuntu 22 systems. Please note a known issue affecting Ubuntu 22 repositories when using apt.
OP-67434 Dynamic Thresholds configuration is now available, providing visualization of current threshold values added or those awaiting data. Additionally, the opsview-sys-master component is installed and configured on the Orchestrator host as part of the setup-everything.yml playbook, managed by Opsview Deploy. Alternatively, the sys-master-install.yml playbook can be used for standalone installation and configuration.
OP-67436 Updated Opspack: Export - Capacity Planner (v1.2.0). Increased the NRPE timeout for the Cap Plan Export - Server - Utilization Service Check to 20 seconds.
OP-60925 Unmanaged databases can be integrated with Opsview using a non-root user.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-65816 The certificate validation process now successfully handles certificates generated by easyrsa (using server-cert PKI command) that contain a mix of FQDNs, IP addresses, and email addresses in their Subject Alternate Names (SANs) list.
OP-67080 Remotely managed collectors can be deployed with or without SSH tunnels, regardless of whether the deployment uses separate registry or messagequeue servers.
OP-68638 Fixed an issue with the SNMP Traps feature where traces could not be started correctly due to messagequeue permissions.
OP-67684 Fixed the following issues in the check_nrpe plugin:
  • check_nrpe and any custom uploaded plugins would not function correctly in Service Checks with Invert Plugin Results enabled.
  • check_nrpe could not communicate with NSClient++ or Opsview Agent on systems using older ciphers.
  • check_nrpe error messages have been made more consistent and informative.
  • Configuration issues in Service Checks using check_nrpe no longer prevent Apply Changes but are now reported during Service Check execution.
OP-68659 Fixed broken link to Default thresholds on the Interfaces tab within Host configuration.
OP-68984 Fixed an issue where the scheduler would restart due to missing agent_config keys in messages.
OP-64009 Errors during scheduled NetAudit collection are now logged to syslog rather than being lost.

Opsview 6.10.0 Copied

Released: 17 July 2024

Highlights Copied

These are the highlights of this release:

New features and enhancements Copied

These are the highlights of this release:

Issue key Description
OP-45872 Since Opsview no longer provides any plugins requiring PowerShell on collectors, PowerShell is excluded from fresh Opsview installations. However, existing Opsview-provided PowerShell will continue to be upgraded and now uses version 7.4.2.
OP-63619 Introduced the ability to select an Alert Type for SNMP interfaces. Existing SNMP interfaces will continue to use the Normal alert type, which maintains their current behaviour. The new Dormant alert type is now available for interfaces that are expected to be down, and detects if their admin status changes to up unexpectedly.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-56850 When a host check recovers from dependency failure, while its dependent checks remain in a dependency failure state, the output now displays Dependency failure: Host X is recovering.
OP-60213 Apache Tomcat used by the Reporting Module has been upgraded to 9.0.89 to address security vulnerabilities.
OP-63085 Updated Opspack: Cloud - GCP (v1.0.6). Reduced CPU utilization for the check_gcp plugin when running multiple concurrent checks, and made argument passing more secure.
OP-64217 The dataserver component now logs error messages to capture details of any MessageQueue connection failures.
OP-66858 The restart snmpd playbook task now runs successfully when deploying or upgrading Opsview, irrespective of default OS snmptrapd user.
OP-67404 Fixed several minor UI issues on the Collector Management page:
  • Last upgrade times (in the table and modal dialogue) are now shown in local time.
  • Navigation bar category buttons deselect correctly.
  • The Last Heartbeat column is no longer displayed.
  • Actions that affect a whole cluster (delete and upgrade) are disabled when the cluster is busy.

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"]

Was this topic helpful?