## Update: 28 Februaary 2022 (6.4.33)
| ID | Summary |
| 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 due to DCOM hardening |
## Update: 12 January 2022 (6.4.32)
| ID | Summary |
| OP-50538 | Patch log4j security vulnerability with version 2.17.1 (CVSS 6.6) |
## Update: 21 December 2021 (6.4.31)
| ID | Summary |
| OP-50329 | Patch log4j security vulnerability - CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 |
## Update: 21 December 2021 (6.4.30)
| ID | Summary |
| OP-47012 | SQL Injection possible in rest/snmptrap/debug (CVSS: 7.1) |
## Update: 28 June 2021 (6.4.29)
| ID | Summary |
| OP-43658 | Revisit rules that govern what is classed as a degraded collector |
## Update: 18 May 2021 (6.4.28)
| ID | Summary |
| OP-43654 | Improve performance characteristics of the opsview-datastore process to reduce load on Collectors |
## Update: 15 April 2021 (6.4.27)
| ID | Summary |
| OP-43866 | Fixed a bug in the UI with automatic activations failing to fall back to the manual activation page in the event of an issue |
## Update: 9 March 2021 (6.4.26)
| ID | Summary |
| OP-43657 | Datastore using up available disk space in a very short period of time |
## Update: 15 February 2021 (6.4.25)
| ID | Summary |
| OP-42366 | Flow collector rpc timed out dashlet errors |
| OP-41003 | Upgrade NFDump to fix multiple vulnerabilities |
## Update: 2 February 2021 (6.4.24)
| ID | Summary |
| OP-43744 | Ensure database ID's 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 1 hour regardless of their activity |
| OP-39365 | Fixed an issue where check and retry intervals for SNMP Polling Servicechecks were incorrectly set to 0 |
## Update: 7 January 2021 (6.4.23)
| ID | Summary |
| OP-42418 | Fixed 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 | Users will be able to have 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 | Improve process to handle SNMP Trap user config when upgrading or re-deploying Opsview Monitor |
## Update: 09 November 2020 (6.4.20)
| ID | Summary |
| OP-41675 OP-41787 | Fix 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 | Fix Acknowledgement issues where an object appears to be acknowledged but the comment and author appear as unknown or blank |
| OP-39836 | Improve database deadlock handling to increase reliability and operational continuity of the Opsview Monitor System |
## Release: 28 October 2020
This section lists general defects across the product that have been addressed in Opsview Monitor 6.4 release. Note that any fixes from previous release dates are rolled up into this latest release.
| ID | Summary |
| OP-37615 | Solved **Test Connection** functionality issues within NetAudit in cases where results were not displayed |
| OP-31097 OP-22196 | Increased the restriction of the number of metrics/plots from 10 to 30 for Investigate window, [Graph Tab](🔗) and [Performance Graph Dashlets](🔗) |
| OP-34619 | Graph refresh button will now work after zooming in and going back to the initial view |
| ODI-3156 | Adjust thresholds for self-monitoring result sender message queue Service Check |
| OP-37941 | New Host Template modal window has incorrect Tab and Field names |
| OP-37932 OP-38103 | Resolve data issues within BSM database tables that were affecting the accuracy of BSM Reports |
| OP-37485 | Improve error message when Importing Monitoring Plugins, taking into consideration Security best practices |
| OP-37566 | Improved error messages across the product |
| OP-36938 OP-27502 OP-27738 | Resolve general Dashboard sharing Issues |
| OP-38854 | Solved VMware Automonitor issues when trying to scan objects nested in folders |
| OP-39032 | Coreutils crontab entries will not be lost after upgrades |
| OP-39509 | Further improvements not to lose Coreutils crontab entries after upgrades |
| OP-39293 OP-39133 | Fixed AutoMonitor issues encountered when populating variables and finding Opsview root Host |
| OP-38416 | As part of an optimised work of the Object Lookup within the Notification Profile, the following issues have been addressed A role with only NOTIFYSOME will now work correctly for notifications Host notifications are now correctly removed, where a relevant service does not belong on it See Release Notes - What’s New!, General Product Improvements |
| OP-31157 | Resolved an issue where the results-dispatcher was not clearing/refreshing its cache when Applying changes |
| OP-24423 | When a Host or a Service Check has been created with the same name as a previously deleted object, it will no longer inherit previous states |
| OP-37971 | Resolve issues where Downtime was allocated to the incorrect Host/Device |
| OP-39662 | Downtime Manager component improvements to avoid failures in situations where object_ids are missing from Database |
| OP-39591 | Solved a REST API issue where Downtime could not be removed from Hots or ServiceChecks using filtering |
| OP-41863 OP-41399 OP-39606 OP-39058 | Solved issues where RPC requests were not entirely parallelized and carried out performance tuning to improve the resilience of message queue |
| OP-37834 | In scenarios where Service Checks are in dependency failure and a manual recheck is performed, returning a different state (e.g. UNKNOWN, WARNING or OK). The Service Checks state will be set back to dependency failure in the next Service Check interval if the dependency failure still exists |
| ODI-2523 | Solved issues with check_snmp_loadavg returning Invalid results |
| ODI-5966 | Addressed cases where some plugins were exposing sensitive information |
| ODI-5178 ODI-3798 | Fixed encoding and result issues with _Office365 - Exchange - Service Status_ Service Check |
| ODI-3579 | Solve Unicode issues with the Result Exporter Component |
| ODI-5725 ODI-5726 | Fixed status resolution for Queue Bytes, Queue Count, Blob Availability and File Availability Service Checks part of the [Cloud - Azure - Storage Accounts](🔗) Host Template |
| ODI-5854 | Fixed unicode conversion error for Services Checks from [Cloud - Azure - Health Availability Status](https://www.opsview.com/product/system-monitoring/azure/azure-monitoring/cloud-azure-healthavailabilitystatus) Host Template part of the [Cloud - Azure Opspack](🔗) |
| ODI-4825 | The following [Cloud - Azure Opspack](🔗) related Service Checks will have default threshold values from this update onwards: - Azure - VMSSVM - Percentage CPU - Azure - VMSS - Percentage CPU - Azure - VM - Percentage CPU - Azure - SQL DB Managed Instance - CPU Percent - Azure - App Service Plan - Percentages |
| ODI-4524 | A new variable (_AZURE_COMPUTER_NAME_) has been added to the following _Cloud - Azure Opspack_ related Service Checks to receive the correct metrics values when a monitored Windows VM is part of a domain. - Azure - Windows VM - Heartbeat - Azure - Windows VM - Logical Disk Space - Azure - Windows VM - Memory - Azure - Windows VM - Processor Queue Length - Azure - Windows VM - Processor Time - Azure - Windows VM - System Uptime Please refer to [Cloud - Azure - Windows VMs](🔗) Host Template documentation for more information. |
| ODI-3579 | Solve Unicode issues with the Result Exporter Component |
| ODI-4849 | Provide support for CacheManager component when TLS is not enabled |
| ODI-4979 | Performance Data will be parsed and graphed correctly for Service Checks with multi-line output |
| ODI-3719 | Contact variables will be now available to be used by the ServiceNow Notification |
| ODI-6266 | _OS - VMware vSphere Opspack_: The vSphere - Host - Health Issues service check within the OS - VMware vSphere ESXi Host Host Template has been updated to now correctly display the sensor type field for numeric sensors. Previously, every numeric sensor listed would falsely display the type of the first sensor in the list. Additionally, the VSPHERE_ESXI_EXPECTED_ELEMENT_ISSUES parameter has been updated to take a list of names as a single record of RFC 4180 defined CSV format with wildcards. This means that through quoting, users can now include element names that themselves contain commas |