OP5 Monitor ["OP5 Monitor"]["Release Notes"]

ITRS Opsview 6.x Release Notes

Overview

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 Opsview 6.x Compatibility Matrix. For details on installation, administration, and usage, you may refer to Opsview Monitor documentation.

Opsview 6.7.3

Released: 21 June 2022

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-49196 Dataserver: Implement API endpoint parameter validation.
OP-49679 Some components are missing basic self-monitoring.
OP-52106 Excessive memory and CPU usage by webappserver.
OP-52483 Opsview Cloud and Opsview Monitor 6.7.2 PRE release activities.
OP-52862 Upgraded Jasper DB has incorrect user roles state leading to Jasperstudio failures.
OP-53020 Clustered Acceptance tests fail due to passives that went missing.
OP-53429 Host Modal Service Check testing is broken.
   

Opsview 6.7.0

Released: 6 April 2022

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-50137 Bumped Opsview minimum version to 6.6.7 for WMIC Opspacks.
OP-51972 BSM expand tooltip drawn badly.
OP-51897 Autodiscovery scan fails for EC2 VA.
OP-51776 Check deploy does not notify for Check for failed connections.
OP-51687 MySQL RPM repository key that is used by Opsview has expired.
OP-51642 The check-deploy fails with load balancer errors.
OP-51618 MySQL APT Repository key that is used by Opsview has expired.
OP-51458 The check_azure shows different tenant error messages intermittently.
OP-51445 Services fail to start on RHEL-8 due to mismatched glib version.
OP-51139 Running network-topology-install.yml playbook alone fails.
OP-50940 Steps for migrating Opsview 6 to new hardware can no longer be followed by users.
OP-50910 Public Deploy Wrapper not pulling down correct deploy version.
OP-47772 Remove HEAD suffix from version number in UI (My System: System Overview).
OP-47716 4 Loadbalancer tasks are taking 15 — 35 minutes.
OP-47391 Cannot query SNMP devices where IfDescr is blank.
OP-47322 Microsoft Teams and Slack notifications do not include an icon or emoji for BSM notifications.
OP-46705 check_k8 - METRIC UNKNOWN - dict object has no attribute split.
OP-45837 Kubernetes Opspack — multiple service checks failing for Azure Pods.
OP-42096 When Kubernetes is not running a number of service checks do not handle it seamlessly.
   

Opsview 6.6.8

Released: 7 March 2022

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-50137 Bumped Opsview minimum version to 6.6.7 for WMIC Opspacks.
   

Opsview 6.6.7

Released: 28 February 2022

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-46827 Opsview AES256 and AES256c support.
OP-47322 Microsoft Teams and Slack notifications do not include an icon or emoji for BSM notifications.
OP-48831 wmic due to fail on latest Windows update because of DCOM hardening.
OP-49385 Implemented NT node status UI.
OP-50536 Microsoft 365 service status checks now fail due to the API being deprecated.
OP-50538 Patch Log4j security vulnerability with version 2.17.1 (CVSS 6.6).
OP-50926 Updated vSphere Opspack with version bump and supported both Opsview and vSphere versions.
OP-51043 Investigate PowerShell script performance solutions.
OP-51072 Investigate Netflow ignoring incoming data.
OP-51139 Running network-topology-install.yml playbook alone fails.
   

Opsview 6.6.6

Released: 12 January 2022

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-50777 ProCheckUp - NetAudit remote code execution vulnerability (CVSSv2: 8.5).
OP-50538 Patch Log4j security vulnerability with version 2.17.1 (CVSS 6.6).
OP-50537 RHEL7: Let's Encrypt certificates need update to ca-certificates.
OP-50329 Patch Log4j security vulnerabilities (Highest CVSS v2: 10.0).
OP-50232 Deployments broken on machines without Cache Manager installed.
OP-49919 Fixed package permissions for opsview-powershell.
OP-49877 repository-setup.yml fails on RHEL-7.
OP-49746 The orchestratorclusterhosts command line tool errors.
OP-49670 BSM notifications do not work for PagerDuty.
OP-49113 Debian 8 to 10 upgrade causing increased datastore CPU and memory usage.
OP-47375 Disable TLS 1.1 on the Opsview-Agent.
OP-46722 Offline cluster — results are lost when cluster is offline.
   

Opsview 6.6.5

Released: 21 December 2021

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-50329

Patch Log4j security vulnerabilities:

  • CVE-2021-44228

  • CVE-2021-45046

  • CVE-2021-45105

OP-50055 Cluster Health broken when run in different time zones (only impacts Opsview 6.6.4).
   

Opsview 6.6.4

Released: 24 November 2021

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-46722 Offline cluster — results are lost when cluster is offline.
   

Opsview 6.6.3

Released: 10 November 2021

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-47963 Host and service remain handled even after the downtime is cancelled.
OP-48910 Network Topology: Loopback address shows as a separate node.
OP-48761 detect_neighbours does not fail when not passing the cmd key.
OP-48310 Auth_tkt removal: NetAudit uses Session Manager permissions.
OP-48309 Auth_tkt removal: Reports use Session Manager permissions.
OP-48144 Microsoft 365 - Exchange - Email Activity service check can return empty values.
OP-45719 Plugnpy does not handle negative numbers when specifying conversion factors.
OP-45428 Changed output from vSphere datastore check.
OP-37093 Updated Angular and dependent Node Modules.
   

Opsview 6.6.2

Released: 16 September 2021

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-37751 Interface Poller fails when more than 400 interfaces are selected.
OP-42050 Interface Poller passive check failure when there are too many interfaces.
OP-42116 Azure - Windows VM - Shutdowns failing due to failure to parse date string.
OP-42242 Broken images on host template icons.
OP-43119 Azure Zero Dimension and Timegrain Bugs.
OP-43121 Azure variables can be incorrect when upgrading to the new Opspack if Host Name in Opsview is not the resource being monitored.
OP-44276 Azure log analytics environment setup broken.
OP-44311 Azure Elastic Pool automated tests are consistently failing when run in the pipeline.
OP-46316 Azure - Network Watcher - Connection Monitors check fails for problem states.
OP-46421 Azure Elastic Pool checks almost all failing with unhelpful error.
OP-47143 Not possible to add over 300 interfaces to a host because of an error when creating the audit log record.
OP-47229 Authentication through OAUTH2 is not working.
OP-47666 Fixed Chrome 92 test failures in opsview-web-ui-ng.
   

Opsview 6.5.9

Released: 28 February 2022

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-50536 Microsoft 365 service status checks now fail due to the API being deprecated.
OP-48831 wmic due to fail on latest Windows update because of DCOM hardening.
   

Opsview 6.5.8

Released: 19 January 2022

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-50538 Patch Log4j security vulnerability with version 2.17.1 (CVSS 6.6).
OP-50777 NetAudit remote code execution vulnerability (CVSSv2: 8.5).
   

Opsview 6.5.7

Released: 21 December 2021

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-50329

Patch Log4j security vulnerabilities:

  • CVE-2021-44228

  • CVE-2021-45046

  • CVE-2021-45105

   

Opsview 6.5.6

Released: 21 December 2021

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-47012 SQL Injection possible in rest/snmptrap/debug (CVSS: 7.1).
   

Opsview 6.5.5

Released: 9 August 2021

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-42050 Interface Poller passive check failure when there are too many interfaces.
   

Opsview 6.5.4

Released: 9 June 2021

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-38860 Improvements to opsview-watchdog PID handling; required for faster environment recoveries.
OP-41441 Brief loss of navigator when clicking Apply Changes.
OP-43120 Improvements to Azure Network Watcher documentation and configuration.
OP-38138 Upgraded Ansible in opsview-deploy.
OP-41373 Passive Checks to inherit Time Period from the Host (rather than assume 24 hours).
OP-42051 Upgraded check_cisco_ipsla.
OP-42105 Improvements to AWS opspack error messages.

OP-42106

OP-43122

Corrected opspack deprecation warnings.
OP-43654 Improvements to opsview-datastore performance on Collectors and the Orchestrator.
OP-43658 Revisited rules that govern what is classed as a degraded Collector.
OP-43866 Fixed an issue where fallback to manual activation in the UI was not working.
OP-44219 Improvements to cluster health logic so Collectors recover much more quickly in the UI.
OP-44228 Improvements to security with handling MySQL passwords in deploy.
OP-45691 Autodiscovery — allow for disabling of ICMP tests for use in secure environments.
OP-45839 Autodiscovery — services and ports are not discovered after the initial 5.
OP-46009 Display Monitoring Clusters in alphabetical order in the Host edit page, not by order of creation.
   

Opsview 6.5.0

Released: 7 April 2021

Issues fixed

These are the issues we have fixed in this release:

Issue key Description
OP-38962 Host and Servicechecks outside of their check period will have their previous state restored after dependency failure recovery.
OP-43657 Datastore using up available disk space in a very short period of time.
OP-42366 Flow collector rpc timed out dashlet errors.
OP-41003 Upgraded NFDump to fix multiple vulnerabilities.
OP-43744 Ensure database IDs generated by the opsview-orchestrator process in certain circumstances use the correct auto_increment_increment setting rather than increasing sequentially, to avoid creating problems with MySQL replication.
OP-42731 Fixed an issue with the opsview-result-recent process communicating to the MySQL database which resulted in messages not being processed in a reasonable time.
OP-43466 Fixed an issue in the UI where authenticated users would be logged out after one hour regardless of their activity.
OP-39365 Fixed an issue where the check and retry intervals for SNMP Polling Servicechecks were incorrectly set to 0.
OP-42418 Fixed an issue where SNMP - MIB II “Uptime Restart” check would display UNKNOWN status when stale after receiving no passive updates, rather than the intended OK status.
OP-42745 Enterprise customers who monitor a large number of devices will experience a loading time improvement on the Navigator page.
OP-36263 Better visibility on Opsview Cluster and Collectors Health Status and monitored host impact in the event of a monitoring operation disruption.
OP-38887 Resolved an issue where CouchDB compactions were not working correctly causing disk usage on Opsview Servers (Master or Collectors) to increase rapidly.
OP-28531 Improved process to handle SNMP Trap user config when upgrading or re-deploying Opsview Monitor.

OP-41675

OP-41787

Fixed Schedule Downtime issues in situations when:

  • After cancelling a scheduled downtime for an object, the object is still shown in downtime in the Investigate window but the author and expiry time appear as unknown or blank.

  • Objects are not shown in downtime in the Investigate window but they were scheduled to be in downtime.

OP-40386 Fixed Acknowledgement issues where an object appears to be acknowledged but the comment and author appear as unknown or blank.
OP-39836 Improved database deadlock handling to increase reliability and operational continuity of the Opsview Monitor system.
   

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