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 6.x release version of Opsview Monitor. Note that any fixes from previous release dates are rolled up into the latest release.

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.7.x and older release notes, you can still access them at the Opsview Knowledge Center.

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

Opsview 6.8.9 Copied

Released: 7 December 2023

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-43712 The Erlang, CouchDB, RabbitMQ, HAProxy, and Kerberos versions within Opsview have been upgraded to mitigate security vulnerabilities.
OP-59446 The Process Map dashlet indicators now display an Investigate menu option that provides access to detailed information about the corresponding monitored objects.
OP-62095 As part of this upgrade, Opsview can now distinguish between Opsview-provided monitoring files (plugins, event handlers, and notification scripts) and those uploaded by users. During this process, any user-uploaded files with the same name as an Opsview-provided file will be overwritten. These overwritten files can be re-imported using the standard documented procedures, as long as any naming conflicts are resolved. The old files on the orchestrator system can be found in the /opt/opsview/monitoringscripts/backup/ directory, timestamped with the upgrade date. However, any edits made solely on collector systems will be overwritten when sync_monitoringscripts is executed after the upgrade.

This release also includes the following updates:

  • The check_plugin_output plugin has been deprecated and is now removed from the system if it is not currently being used by a Service Check or Host Check command. If you are still using the check_plugin_output plugin, it will now be considered a user-uploaded plugin.
  • The REST API endpoint /rest/config/plugin now returns an origin_id field. A value of 0 means the plugin is provided by Opsview, while a value of 1 means the plugin was uploaded by a user.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-56496 The login page now automatically reloads after an hour of inactivity since rendering to prevent anti-CSRF token errors and enhance user experience.
OP-57836 Opsview has been updated to prevent unnecessary code compilation attempts. Previously, an alert would be triggered whenever an attempt was made to compile code using the GCC command in a Linux environment.
OP-61771 The Scheduler version stored in the Opsview database is automatically updated with each Scheduler package update and restart.
OP-62356 Collectors can be added to a remotely managed cluster regardless of the alphabetical order of their hostname. In the event of a message queue setup failure, the playbook no longer becomes unresponsive indefinitely.
OP-63677 Automonitor scan logs can now properly handle and display multiline errors. This resolves a previous issue on Windows machines where multiline PowerShell error messages were interpreted as invalid JSON, leading to incorrect display in the UI.
OP-64069 Fixed permission problems with external databases, ensuring smooth database backup and restore processes in both Opsview Cloud and Opsview Monitor deployments.

Opsview 6.8.8 Copied

Released: 1 November 2023

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-61526 You can now view the Collector Management upgrade log files in the user interface, which makes it easier to debug upgrade issues.
OP-61567 The following Opspacks have been updated:
  • Database - Etcd (v2.1.0) — The Database - Etcd Host Template now supports the ETCD_TLS variable for TLS connections.
  • Database - MySQL Server (v2.2.0) — The Database - MySQL - Agentless Host Template is now available for monitoring MySQL installations without a monitoring agent installed. You can also use the new MySQL Max used connections - higher thresholds service check.
OP-61665 The address of the remote system is now included in the audit log record when a collector registration or cluster upgrade is started. This allows you to track where the remote registration request was made.
OP-61666 Remotely managed collectors can now automatically monitor their own disks, so you can track their status without having to manually add the disks to your monitoring configuration.
OP-61783 A new script called orchestratorimportscripts has been added to opsview-orchestrator. This script helps Opsview Monitor administrators install event handlers, notification scripts, and other files in the /opt/opsview/monitoringscripts directory, ensuring that all files are placed in the correct location with the correct permissions and ownership. During the upgrade, any directories that have previously been created under /opt/opsview/monitoringscripts/etc, /opt/opsview/monitoringscripts/plugins, /opt/opsview/monitoringscripts/notifications, and /opt/opsview/monitoringscripts/eventhandlers will be updated to have the owner root, the group opsview, and the permissions 770.
OP-61784 The post-upgrade steps for updating Opspacks have been updated, see Upgrade Opspacks. Opsview has changed how to import plugins and Opspacks:
  • Plugins can now only be imported via the UI or REST API, instead of copying them directly to the filesystem.
  • Plugin or plugin-related Opspack files cannot be imported if their name clashes with an existing Opsview-provided plugin. If this happens, you should rename the file you are trying to upload.
  • Opspack imports now correctly display file clashes in the UI.
  • Plugin help text gathering has been improved, and more Opsview-provided plugins will have help text accessible in the UI. The check_wmi_plus.pl plugin now reports summarized INI help unless the --inihelp option is provided.
The following Opspacks have been updated to clean up files and plugins:
  • Application - Microsoft Hyper-V Agentless (v2.2.4)
  • Application - WebLogic (v2.1.2)
  • Database - PostgreSQL (v2.0.2)
  • Infrastructure - APC (v2.0.2)
  • Infrastructure - Sensatronics (v2.0.2)
  • Network - Cisco (v2.0.2)
  • Network - Cisco Advanced (v2.0.2)
  • Network - Foundry (v2.0.2)
  • Network - Juniper (v2.0.2)
  • Network - NetScaler (v2.0.2)
  • OS - Linux SNMP (v2.0.3)
  • OS - Windows WMI - Base Agentless (v2.1.4)
  • OS - Windows WMI - DNS Agentless (v2.1.4)
  • OS - Windows WMI - IIS Server Agentless (v2.1.4)
  • OS - Windows WMI - Terminal Services Agentless (v2.1.4)
  • SNMP - MIB-II (v4.1.3)
OP-62420 Collector Management now allows you to access the log API while an action is in progress, such as during a registration or update. This means that you do not have to wait for the action to complete or time out before you can view the logs.
OP-62680 Collector Management has added the following options to help identify and troubleshoot registration and upgrade issues:
  • -v or --verbose option added to collector registration to the collector upgrade utility.
  • opsview-deploy is invoked with -vvv when the verbose option is specified.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-38891 Fixed an issue where service dependencies were not correctly handled when multiple service checks were created. Previously, child service checks would continue to run even after the parent service check had failed. This could cause incorrect notifications to be sent out.
OP-56894 Fixed an issue where the setup-monitoring playbook failed when change logging was enabled. This means that you can now register and update remotely managed collectors when the change logs are enabled.
OP-62062 Fixed an issue where the font becomes invisible when the mobile app is in dark theme.
OP-62080 Fixed several issues in the Collector Management user interface, including:
  • The new cluster modal does not check the Network Topology license, so the check box is always enabled.
  • The display message at the end of successful registration has been changed to Successful registration.
  • When registration fails, the upgrade failed toast message has been changed to a registration error message.
  • The cluster name in the modal is not wrapped, has no tooltip, and can be truncated.
OP-62633 Audit events for remote collector registration request and completion have been moved from the CONFIG to the ACTION category.
OP-62656 The Hyper-V VA image can now be used on a disk that is larger than 20 GB, which allows for more data to be stored and used. This unblocks Hyper-V VA deployments. Note that the VA contains Opsview version 6.8.7.
OP-62838 Session tokens are now more secure and are no longer displayed on the command line to improve security. This means that the session token is not passed to opsview-deploy or curl, or it is not saved in the Ansible log, logged command line, or verbose logging (-vvv).
OP-62933 The remote collector upgrade utility now logs events to help users diagnose problems. Additionally, startup problems with the upgrade utility are now reported to the data server.
OP-63073 Collector registration now works on all supported operating systems. Previously, using an old version of curl would prevent you from registering collectors.
OP-63102 Fixed an issue where the WebSocket sent multiple messages to the front end when status changes occurred in a Collector Management cluster. This could cause messages to be displayed to the user more than once.

Opsview 6.8.7 Copied

Released: 28 September 2023

Highlights Copied

These are the highlights of this release:

For more information, see What’s New in Opsview.

New features and enhancements Copied

These are the new features and enhancements of this release:

Issue key Description
OP-58270 During the upgrade, collectors will be automatically switched to be self-monitored by the cluster when they use SSH tunnels to connect to the master. This means that you no longer have to manually reconfigure collectors when you want to use SSH tunnels to connect to the master.
OP-59667 The dataserver progress API has been updated to handle reports with an attached log file for remotely managed collector registrations and upgrades. This lets Opsview administrators diagnose problems with remotely managed collector registrations and upgrades by viewing the attached log file.
OP-59908 The following Opspacks have been updated: Application - Opsview (v3.1.0), Opsview - Self Monitoring (v3.0.0). Also, the Opsview - Login Service Check now supports systems with and without TLS enabled.
OP-59909 You can now see toast messages when triggering an upgrade. This will notify you of collector upgrade events so that you can be aware of the status of your upgrades and take any necessary action.
OP-61657 The dataserver now provides reload events to all applications. This allows applications to react to changes in the dataserver, if necessary. Previously, the orchestrator sent reload events to the dataserver, but these were ingested by Network Topology. Now, the events are ingested by the dataserver and then passed to any services that have subscribed to reload events.
OP-61665 The address of the remote system is now included in the audit log record when a collector registration or cluster upgrade is started. This allows you to track where the remote registration request was made.
OP-62094 The Apply Changes modal now shows how many configuration changes have been updated from the command line (by the SYSTEM user). The opsview_sync_ldap now also logs progress messages to the Audit Logs using the ACTION category (instead of the CONFIG category).

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-59115 The Orchestrator and Scheduler now shut down correctly. This prevents old Orchestrator and Scheduler processes from running and causing the Opsview service to be in a bad state after an upgrade.
OP-61939 Remote collectors can now be installed using the same repository as the master. This simplifies the installation process and makes it easier to keep remote collectors up-to-date.
OP-62341 Administrators are now notified of failures to upgrade remotely managed clusters, which allows them to investigate the failures and take appropriate action.

Opsview 6.8.6 Copied

Released: 31 August 2023

Highlights Copied

These are the highlights of this release:

For more information, see What’s New in Opsview.

New features and enhancements Copied

These are the new features and enhancements of this release:

Issue key Description
OP-31981 Opsview administrators can now install, configure, and update opsview-results-exporter with opsview-deploy. This will save time for deployment or upgrades, mitigate the risk of human error, reduce confusion due to inconsistent deployment methods, and ensure that you are always using the latest, secure component configuration.
OP-58460 The readability of command-line arguments in the user interface has been improved by using a monospaced font, which makes the text easier to read.
OP-58478 Opsview administrators can now use the web UI to manage collector upgrades remotely. This means that you no longer need to access the collector command line to upgrade collectors.
OP-58520 Websocket connections from the dataserver are now permitted for secure authorized access to display collector update progress.
OP-60324 This includes the following changes:
  • A new collector management websocket service has been created.
  • The collector management reducer and effects have been updated to insert data into the store.
  • Websocket error cases have been handled and the store has been updated.
OP-61021 The current Opsview version on the orchestrator host is now accessible through the database.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-38325 You can now delete users and bulk hosts without any errors when the changelog is enabled.
OP-43652 State history retention and audit log retention are decoupled. The new State History Retention setting in My System covers downtimes, acknowledgments, and object event history. This also fixed UI issues during post-Apply Changes backups. For more information, see the My System > Options documentation.
OP-56199 This change ensures that setup-monitoring can be run successfully on all systems with more than 9 collectors without encountering a deadlock error. This error occurs when setup-monitoring tries to register too many collectors at once.
OP-57192 Updated product documentation links to ensure that they direct users to the correct sections in the ITRS Opsview documentation.
OP-60167 The opsview-netaudit-collector package now includes the additional patched files listed in the Makefile to ensure that the package works correctly.
OP-60292 The Collector Management page has been updated to ensure that all elements are aligned and styled consistently throughout the user interface.
OP-60554 The responses from the dataserver have been refactored to return JSON instead of HTML. This makes error handling easier when calling the dataserver API.
OP-61307 The deploy variable that was previously known as opsview_results_exporter_custom_outputs is now called opsview_results_exporter_outputs. For more information, see the Exporting Results and Results Exporter documentations.
OP-61402 Remotely managed collectors can now be installed and upgraded on both standard systems and rehomed systems.

Opsview 6.8.5 Copied

Released: 20 July 2023

Highlights Copied

These are the highlights of this release:

For more information, see What’s New in Opsview.

New features and enhancements Copied

These are the new features and enhancements of this release:

Issue key Description
OP-49589 Perl modules have been updated to fix security vulnerabilities. The following Opspacks have been updated to use the new modules:
  • Application - Apache HTTP Server (v2.0.1)
  • Application - Apache Solr (v2.1.1)
  • Application - Dell Hardware (v2.0.2)
  • Application - Elasticsearch (v2.0.2)
  • Application - Microsoft Hyper-V Agentless (v2.2.3)
  • Application - Opsview BSM (v2.0.1)
  • Application - Opsview (v3.0.5)
  • Application - WebLogic (v2.1.1)
  • Cloud - Salesforce (v2.0.1)
  • Cloud - Service Cloud (v2.0.1)
  • Database - Microsoft SQL (v2.1.1)
  • Database - MySQL Server (v2.1.1)
  • Database - Oracle RDBMS (v2.0.1)
  • Database - PostgreSQL (v2.0.1)
  • Network - Cisco IPSLA (v2.2.1)
  • Network Services - Email (v2.0.1)
  • OS - Linux SNMP (v2.0.2)
  • OS - Unix Agentless (v2.0.1)
  • OS - Windows WMI - Base Agentless (v2.1.3)
  • OS - Windows WMI - DNS Agentless (v2.1.3)
  • OS - Windows WMI - IIS Server Agentless (v2.1.3)
  • OS - Windows WMI - Terminal Services Agentless (v2.1.3)
  • SAN - NetApp (v2.0.2)
  • Service Provider - Amazon (v2.0.1)
  • SNMP - MIB II (v4.1.2)
OP-51093 The Sentinel RMS has been updated to ensure that Opsview licensing continues to function.
OP-54854 The NOTICE logs now include more detailed information about SSH tunnels that fail to set up ports.
OP-57999 MySQL no longer requires RELOAD permission on new or upgraded systems.
OP-58475 The scheduler now handles requests for collector updates. Additionally, it invokes the update utility and sends the appropriate response message.
OP-58764 The dataserver now has an API that allows users to update collectors (only for the update cluster). Additionally, the dataserver sends a request message to the scheduler and handles the response from the scheduler.
OP-60234 The command line options for registering collectors have been improved. The help text now includes both long and short command line options, and the options are consistent with those used for collector upgrades. Additionally, a new option, -k --insecure, has been added to disable certificate checks when using the dataserver APIs.
OP-60242 The validation of create and delete requests in the Collectors interface has been improved.
OP-60327 Opsview Monitor can now be deployed on OEL 8 systems.
OP-60455 The ITRS Infrastructure Agent is no longer in beta and can now be used as a stable alternative to the Opsview and NSClient agents. Please refer to the ITRS Infrastructure Agent documentation.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-47629 The Last Check column in Checker has been expanded to fill the width of the column, allowing all of the information to be displayed.
OP-56075 Apache Tomcat and Reports module (JasperServer) have been updated to the latest versions to fix security vulnerabilities.
OP-56868 Updated Opspack: Application - Microsoft 365 (v2.0.8). Fixed an issue where the check_microsoft365 plugin was unable to correctly parse API data for the following Service Checks:
  • Microsoft365.Overview.Identity.Service.Status
  • Microsoft365.Overview.Portal.Service.Status
  • Microsoft365.Exchange.Service.Status
  • Microsoft365.SharePoint.Service.Status
  • Microsoft365.OneDrive.Service.Status
  • Microsoft365.Skype.For.Business.Service.Status
These Service Checks will now display detected issues summarized by their type (incident, advisory, or other) instead of their impact level.
OP-57192 Updated product documentation links to ensure that they direct users to the correct sections in the ITRS Opsview documentation.
OP-60671 For systems with remote databases that are managed by deploy, the orchestrator host will now have the same database vendor and version as the remote host, as long as both hosts are running the same operating system. If you encounter any problems upgrading your databases, please read this support article.
OP-60841 Autodiscovery can now detect Infrastructure Agents running on scanned hosts in most cases. For more information, see Autodiscovery Detection Mapping.

Opsview 6.8.4 Copied

Released: 14 June 2023

Highlights Copied

These are the highlights of this release:

For more information, see What’s New in Opsview.

New features and enhancements Copied

These are the new features and enhancements of this release:

Issue key Description
OP-52775 The Results Exporter component now supports additional field mapping options, including string replacement and querying data from the Opsview system to enhance exported messages. As a result, the component requires additional credential configuration to function properly. After upgrading Opsview, ensure that the command_queue and runtime_database sections from resultsexporter.defaults.yaml are copied into your resultsexporter.yaml file. Then, you need to override the credentials in these sections with the correct credentials. For more information, see Results Exporter administration.
Two new self-monitoring checks will be applied to hosts running a Results Exporter as part of the upgrade. After upgrading Opspacks and the setup-monitoring.yml playbook, run:
  • Opsview - Results Exporter - Command Message Queue Count
  • Opsview - Results Exporter - Command Message Queue Rate
Opspacks updates:
  • Opsview - Self Monitoring (v2.2.0)
OP-56011 The Infrastructure Agent and plugin repositories are now in general availability, which you can access from ITRS GitHub.
OP-56754 Infrastructure Agent now accepts requests from check_nrpe with arguments after -a having the arguments in the right order: check_nrpe -H host -C command -a "arg1" "arg2".
OP-58473 The check-deploy playbook is now run as part of collector updates.
OP-58481 Opsview administrators can now clean up any remotely managed collector upgrades that have stopped responding. Stalled updates are also logged and terminated.
OP-58585 The opsview-deploy package will now upgrade to the latest version before attempting to run any playbook during a remote collector update.
OP-58597 The collector upgrade utility now provides updates on its progress using the Dataserver API. The Ansible log is also included, where applicable.
OP-58599 The web user interface for accessing the datastore has been updated to include views that allow users to easily access data for each cluster or collector.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-52757 Results Exporter now deletes unused message queues at start-up. If any outputs are removed from the component configuration file or commented out, any messages still in the queues will be deleted, and no new messages will be collected for those outputs. To replicate the previous behavior of putting the output into a state where messages are collected but not exported, you can now use the new built-in hold filter.
OP-58373 Only one collector can be registered in a cluster at a time. Previously, registering a second collector before the first one had finished caused errors and deadlocks.
OP-59389 Infrastructure Agent no longer stops working when the hostname does not match the certificate.
OP-59428 When a collector in a cluster is monitoring another collector in the same cluster, checks run via the monitored collector now return working results.
OP-59706 When the default Linux agent is built from the source, it starts up without any errors and creates and uses self-signed certificates in its var directory.
OP-59719 Updates have been made, allowing the opsview-dataserver to:
  • Get installed on systems that do not have opsview_core_secure_wallet_key in user_secrets.
  • Use opsview_core_secure_wallet_key_hash if opsview_core_secure_wallet_key is not present, but the hash is.
  • Use opsview_core_secure_wallet_key_hash, generating it from opsview_core_secure_wallet_key.

Opsview 6.8.3 Copied

Released: 25 May 2023

Highlights Copied

These are the highlights of this release:

For more information, see What’s New in Opsview.

New features and enhancements Copied

These are the new features and enhancements of this release:

Issue key Description
OP-45558 Opsview Deploy logs now include the version number of Deploy at the top of all log files for easier debugging of deploy issues.
OP-52758 Added a new RELOADVIEW permission to control read-only views in the Apply Changes status.
OP-53118 You can now deploy multi-collector clusters in a new installation without having shell access to Orchestrator or a cloud platform. This improves the resilience and scalability of the collector clusters.
OP-57238 The help text is available in every service check included with Windows builds of the Infrastructure Agent when called using the appropriate arguments.
OP-57644 Added local and remote port forwarding to the tunnels, enabling users to use more services without having to open more firewall ports.
OP-58370 New licensing information has been added to the infrastructure-agent plugin repositories for both Linux and Windows.
OP-58471 Collector management now has a new database called opsview-managed-clusters. Similar to the opsview-system-status database, this new database uses the same key format. The timestamps are UTC in ISO format: yyyy-mm-ddThh:mm:ss.ssssss, for instance, 2023-04-12T11:51:03.698321.
OP-58476 The dataserver now supports an API for collector updates.
OP-58583 The update utility now prompts the user for their credentials before authenticating via the REST API. This ensures that the user’s password is not exposed on the terminal. The update utility then uses the acquired session ID to perform the update process.
OP-58584 The admin of a remotely managed collector can now update the utility to ensure the version is updated in user_vars.yml.
OP-58755 Added a new feature that allows the administrators to invoke a collector update API from the collector.
OP-59498 If more than one LDAP realm is set up and one of them lacks the necessary configuration files and folders, the other realms are continuously processed.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-55094 Fixed an issue where users with restricted access to the monitoring servers could access all of the monitoring servers.
OP-57837 When a restore fails, the audit log now shows the error message. The error details are now recorded in the restore log, and the lock is released to make another attempt.
OP-58356 Fixed the Navigator check box visual issue after Apply Changes has completed.
OP-58405 Fixed an issue where Agent Python plugins failed when outputting UTF-8 on some operating systems.
OP-58621 When a backup is restored, the backup IDs continue incrementing correctly without gaps or overlaps.
OP-58681 Default NRPE ciphers have been amended to work with old and new Infrastructure Agent.
OP-58831 Corrected the location path of the extracted plugins, which can be found in <agent-root>/plugins/, when extracting the source build.

Opsview 6.8.2 Copied

Released: 19 April 2023

Highlights Copied

These are the highlights of this release:

For more information, see What’s New in Opsview.

New features and enhancements Copied

These are the new features and enhancements of this release:

Issue key Description
OP-49965 Opsview now uses Nucleon as the default message queue driver for Python components, which can handle workloads with less resource usage.
OP-50915 The window size has been adjusted so that you can better view the interface when performing SNMP polling.
OP-51662 Added columns for Host Group, Host Description, and Host Network Address, and enhanced tooltips for:
  • Host Interfaces Dashlet
  • Top Services By Metric Dashlet
  • Event Graph Dashlet
  • Hashtags
Additionally, the REST API has been updated:
  • /rest/status/performancemetric — the include_hostip parameter has been renamed to include_hostdetails and will now include both the host’s IP address and description if set.
  • /rest/event — the host group path returned is now comma-separated rather than slash-separated, and does not include a leading slash.
OP-53127 Improved Uptrends integration allows you to view Uptrends data within Opsview. This includes real-time user monitoring and synthetic monitoring, both of which can be used to test and monitor the functionality of your website.
OP-53128 When adding a new collector to a cluster without shell access to the Orchestrator, SSH tunnels can now be configured to allow all Opsview (collector-to-orchestrator) traffic to go over a single port.
OP-53145 You can now access the Infrastructure Agent, allowing you to build your own agent from the source code and examine the source code to ensure it is secure and safe to use.
OP-54117 Uptrends integration improvements:
  • Time filters used in calls to the Uptrends API are rounded to the nearest 5-minute interval.
  • Times used in Uptrends API queries follow the local timezone of the Uptrends account.
  • Time filters used to query the data in the service check output are displayed.
OP-54354 Opsview Deploy installs a new Infrastructure Agent for self-monitoring while removing the old Opsview Agent automatically. NRPE checks now respect the NRPE_EXTRA_FLAGS variable. The following Opspacks have been updated:
  • Application - Alfresco (v2.1.0)
  • Application - Docker (v2.2.0)
  • Application - HAProxy (v2.1.2)
  • Application - Microsoft IIS (v2.1.0)
  • Application - OpenSim (v2.1.0)
  • Application - Varnish Cache 3.0 (v2.1.0)
  • Application - Varnish Cache (v2.1.0)
  • Database - Etcd (v2.0.2)
  • Database - Microsoft SQL (v2.1.0)
  • Database - MySQL Server (v2.1.0)
  • Export - Capacity Planner (v1.1.0)
  • Management - Puppet (v2.1.0)
  • Network Services - SSH (v2.1.0)
  • Management - Puppet (v2.1.0)
  • Opsview - Component - Datastore (v5.0.0)
  • Opsview - Component - Load Balancer (v5.0.0)
  • Opsview - Component - MessageQueue (v5.0.0)
  • Opsview - Component - Registry (v4.0.0)
  • OS - Opsview Agent (v3.0.0)
  • OS - Unix Advanced (v2.1.0)
  • OS - Unix Base (v2.1.0)
  • OS - Windows Base (v2.1.0)
  • OS - Windows Event Log (v2.1.0)
OP-55727 The Infrastructure Agent supports existing Windows plugins, so when you switch to the newer Infrastructure Agent, the Windows plugins continue to function.
OP-56209 Windows plugins now return the correct information when an error occurs or when expected arguments are passed. This allows you to monitor metrics on the Windows hosts, such as additional counters and services.
OP-56292 A new CONFIGURECLUSTER permission is now available, allowing you to add empty clusters and manage them remotely.
OP-56692 Updated Opspack: Opsview - Self Monitoring (v2.1.0). Added a new infrastructure self-monitoring host template to Opsview hosts.
OP-57023 All service checks shipped with Linux builds of the Infrastructure Agent now contain help text describing all arguments and configuration instructions.
OP-57264 Agent creates and uses self-signed certificate if no TLS options.
OP-57339 Added host group, host description, and host IP column to dashlets and monitoring pages.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-39297 Improved opsview_sync_ldap script that is used for syncing Opsview users and roles with an LDAP or Active Directory server:
  • Improved logging.
  • Self-monitoring of LDAP sync status in Opsview.
  • Support for multiple LDAP realms.
  • Support for nested LDAP groups.
  • Support for encrypted user secrets.
Group files must now have an .xml extension to be processed correctly. Added Opspack: Opsview - Sync LDAP (v1.0.0)
OP-50697 When a reload happens and a user is deleted but still has an open connection, the component now handles the error and delivers a new map without access.
OP-52840 State Changes component no longer encounters message queue failures with the error message PRECONDITION_FAILED -- unknown delivery tag.
OP-55613 Changed column headers when graphs are exported from:
  • Performance Graph Dashlets
  • Graph Center
  • Service Investigate Graphs
The headers now reflect the exported data instead of being fixed generic labels. This covers the data formats CSV, JSON, and XLSX.
OP-56104 Freshness Checker no longer leaks file descriptors when publishing stale result messages.
OP-56638 The imported.yml file moved up one level into the cfg dir.
OP-56639 Windows Agent runtime now works correctly when you add args to the runtime.
OP-57482 No patch version is disclosed on the Opsview login page.
OP-57549 The GPG key links have been updated.
OP-57551 check_eventlog has been updated.
OP-57605 Nucleon now handles configurable message_ttl_secs the same as kombu.
OP-57662 Fixed an issue in the AF_INET error that was causing the Windows Infrastructure Agent to fail.
OP-57691 Updated Opspack Application - Opsview to v3.0.4. The following Service Checks have been added to monitor the backup process:
  • Opsview - Backups Apply Changes
  • Opsview - Backups Daily
OP-57694 For all supported OSes, the Capacity Planner plugin now returns both stderr if functioning properly and a non-OK state if no information is collected.
OP-57744 MySQL 5.7 and 8.0 database backups now work correctly.
OP-57855 When a restore fails, the audit log now shows the error message. The error details are now logged in the restore log, and the lock is released to make another attempt.
OP-57940 Fixed an issue where incorrect ownership caused host checks from collectors to fail.
OP-58067 After upgrading to a version with the new agent, self-monitoring checks are now working.
OP-58139 When entering customer payload, the My System page no longer stops. Issues with field constraints have also been fixed.
OP-58182 Infrastructure Agent script execution results can now hold at least 16KiB of data. To enable this functionality, set allow_multi_packet_response in the Agent configuration to true.
OP-58282 When running checks with output longer than 4094 characters, Infrastructure Agent for Windows no longer times out.
OP-58325 Upgrading from Opsview Agent to Infrastructure Agent no longer causes a version error message.
OP-58375 The db_mysql now runs properly on every upgrade.
OP-58548 Fixed an issue where the Opsview - Daily Backups service check went critical due to the filesystem backup tar exit code of 1.

Opsview 6.8.0 Copied

Released: 25 January 2023

Highlights Copied

These are the highlights of this release:

For more information, see What’s New in Opsview.

Issue key Description
OP-34170 The database tables now use the same character set consistently.
OP-51975 VMware and HyperV virtual appliances no longer ship with the default SNMP community string configured.
OP-52382 All Opsview MySQL databases, such as opsview, runtime, ODW, and dashboards can now accept complete UTF-8 characters. Upated Opspacks:
  • Cloud - AWS - DynamoDB CloudWatch (v2.2.0)
  • OS - Windows Base Agentless (v2.3.0)
OP-55866 Initial UTF-8 support includes using scandic characters. Upated Opspacks:
  • Infrastructure - Cisco UCS (v1.0.4)
  • Cloud - GCP (v1.0.5)
  • Application - Kubernetes (v1.0.6)
  • Cloud - Azure (v2.2.5)
  • Application - Microsoft 365 (v2.0.7)
  • Cloud - OpenStack (v1.0.5)
  • Opsview - Self Monitoring (v1.3.1)
  • OS - VMware vSphere (v2.0.13)
  • Cloud - Uptrends (v1.0.2)
  • Network - Cisco ACI (v1.0.7)
  • Cloud - AWS (v1.1.1)
OP-55888 Starting with the Opsview 6.8.0 release, you can find the documentation, including the ITRS Opsview Cloud Documentation, at ITRS Opsview Documentation.
OP-56537 All Golang components are now compiled using the updated toolchain. Both the go.mod and go.sum files no longer ship with the product.
OP-56835 The Notification method variable no longer fails when it accepts more than 128 characters.
OP-56943 Removed duplicate validation messages in the NetFlow source IP field.
OP-56987 Fixed a UI issue with the Host Group modal.
OP-57069 Upgrading from Opsview 6.8.0 where UTF-8 data is present now works correctly.

Opsview 6.7.6 Copied

Highlights Copied

Released: 2 November 2022

These are the highlights of this release:

For more information, see What’s New in Opsview.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-24136 You can now configure the monitoring pages with a particular refresh interval and save the changes.
OP-43034 Fixed an issue where NetAudit failed to process messages due to an error found in the configuration file.
OP-44544 You can now use AWS roles in the check_aws_cloudwatch plugin.
OP-45903 The validation field warning messages now display the correct messages when the name value of a variable exceeds 63 characters.
OP-46746 Upgraded Jasper to version 8.1.0 and Tomcat to version 9.0.65.
OP-47063 For a specific user, you can now remove host group access to ensure that modifications are applied appropriately after a reload.
OP-47728 The opsview-data-access is now available for use in the opsview-notification-center component.
OP-48227 You can now search and filter host templates that are available using the Host Templates search field.
OP-50991 You can now view the Network Topology map correctly when the VIEWALL permission has been set.
OP-51966 Corrected tooltip description on the Monitoring Collectors page.
OP-53513 Using vCenter credentials, the ESXi servers (host and guest) can now be monitored without requiring additional credentials.
OP-53812 A new NTVIEWALL permission has been created to prevent viewing any hosts that are not imported within the Network Topology map.
OP-54084 An error when querying recent versions of Elasticsearch has been resolved.
OP-54241 Improved NetFlow Dashlet to provide better visualisation of NetFlow traffic.
OP-54616 Added Capacity Planner integration Opspack using OLD Windows and Linux agents.
OP-55020 Fixed the NetFlow security vulnerability issue that prevented the API command injection (CVSS v2 8.5).
OP-55106 Fixed an issue where the progress bar for applying changes closes quickly before the assertion check is done.
OP-55108 The host icon management now works correctly.
OP-55118 Corrected a typographical error in the Status Access > Network Topology.
OP-55412 Improved performance response of the opsview_flow command.
OP-55413 A TTL (time to live) has been added to any flow requests made through the REST API, so messages will be automatically removed if a flow-collector does not pick up the request within 30 seconds. This avoids a build up of messages if the component is temporarily stopped.
OP-55450 The opsview-flow-collector component has been made more resilient to any messagequeue failures, so it now reconnects automatically.
OP-55548 Specific collectors have been set for flow-collector to load balance the sources manually.

Opsview 6.7.5 Copied

Released: 6 September 2022

Highlights Copied

These are the highlights of this release:

For more information, see What’s New in Opsview.

Issues fixed Copied

These are the issues we have fixed in this release:

Issue key Description
OP-48906 ProCheckUp: Privileged administrative functions no longer require password. When setting up Opsview Cloud system, the NOPASSWD flag has been removed from the users sudo configuration. This ensures users performing administrative functionality are asked to explicitly re-enter a strong password.
OP-51564 Notifications are now triggered not only when an object changes state but also when some configuration changes are applied that would have triggered a notification when the current state happened. This enables Opsview to notify new teams or individuals about existing problems in the system.
OP-52201 ProCheckUp - Opsview Software Version Disclosure (CVSS: 1.8). ProCheckUp performed a round of web app pen testing.
OP-53112 Notifications are now working until service check goes back to an OK state.
OP-53127 Uptrends integration allows real and synthetic monitoring data to be displayed in Opsview Monitor.
OP-53136 You can now run the Agent as a daemon on both Linux and Windows hosts so that it can always be running in the background and available to run checks, even after machine reboot.
OP-53137 You can now install the Agent through the following: a single package file, from apt, or yum repository. This makes the installation for the Agent easier.
OP-53138 You can now install the Windows Agent to monitor your Windows system with a lightweight process.
OP-53142 You can now run and validate all the existing NSClient++ checks against the new agent to prevent losing any checks when switching to the new agent.
OP-53229 Opsview Monitor and Opsview Cloud PRE release activities and preparation for automation runs.
OP-53653 When deploying Opsview, the deployment process completes correctly and no warnings are shown when running setup-everything/opsview.
OP-53844 Implemented service check poller. Built-in checks are now available which return aggregated metrics from data gathered (polled) on a regular schedule. This ensures the aggregated metrics to return more accurate data.
OP-53939 Fixed an issue that generates an error Method not allowed in the Notification Profiles when clicking Objects Selected.
OP-53956 Fixed an issue in SSO/OAuth2 login that led to the Content Security Policy (CSP) error.
OP-53997 Fixed an issue that caused the Access Denied page to refresh every second.
OP-54117 Improved the collection of Uptrends data to be displayed in the Opsview Monitor.
  • Time filters used in calls to the Uptrends API are rounded to the nearest 5 minutes.
  • Times used in Uptrends API queries use the local timezone of the Uptrends account.
  • Display the time filter used to query the data in the service check output.
OP-54140 Fixed an issue that prevented state updates by causing passives to become trapped in the results forwarder cache queue.
OP-54261 Fixed an issue in the sync monitoring script that caused the plugin permission to be broken.
OP-54496 Idle session timer now works correctly before logging out.
OP-54562 Jasper server deployment now installs correctly when using Opsview managed database and external database using TLS.

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?