Fixed Defects
A list of defects fixed in each release
Update: 23 November 2020 (6.3.19)
| ID | Summary |
|---|---|
| OP-41785 | Further Schedule Downtime fixes in situations when after cancelling a scheduled downtime for an object, the downtime entry is correctly removed from the Schedule Downtime view but the object is still shown in downtime in the Investigate window and the author and expiry time appear as unknown or blank. |
Update: 03 November 2020 (6.3.18)
| 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 |
Update: 22 October 2020 (6.3.17)
| ID | Summary |
|---|---|
| OP-40386 | Fix Acknowledgement issues where an object appears to be acknowledged but the comment and author appear as unknown or blank |
Update: 12 October 2020 (6.3.16)
| ID | Summary |
|---|---|
| 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 queues |
Update: 20 August 2020 (6.3.15)
| ID | Summary |
|---|---|
| OP-40907 | Security improvements to ensure all access to CouchDB is restricted by authentication |
Update: 10 August 2020 (6.3.14)
| ID | Summary |
|---|---|
| OP-31157 | Resolved an issue where the results-dispatcher was not clearing/refreshing its cache when Applying changes |
Update: 30 July 2020 (6.3.13)
| ID | Summary |
|---|---|
| OP-39662 | Downtime Manager component improvements to avoid failures in situations where object_ids are missing from Database |
Update: 23 July 2020 (6.3.12)
| ID | Summary |
|---|---|
| OP-40395 | check_opsview_updates service check will display the correct version of the system |
Update: 16 July 2020 (6.3.11)
| ID | Summary |
|---|---|
| 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! |
Update: 03 July 2020 (6.3.10)
| ID | Summary |
|---|---|
| OP-39591 | Solved a REST API issue where Downtime could not be removed from Host or ServiceChecks using filtering |
Update: 18 June 2020 (6.3.9)
| ID | Summary |
|---|---|
| OP-39293 OP-39133 | Fixed AutoMonitor issues encountered when populating variables and finding Opsview root Host |
Update: 02 June 2020 (6.3.8)
| ID | Summary |
|---|---|
| OP-39509 | Further improvements not to lose Coreutils crontab entries after upgrades |
Update: 22 May 2020 (6.3.7)
| ID | Summary |
|---|---|
| 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 |
| ODI-5854 | Fixed unicode conversion error for Services Checks from Cloud - Azure - Health Availability Status Host Template part of the Cloud - Azure Opspack |
Update: 06 May 2020 (6.3.6)
| ID | Summary |
|---|---|
| OP-38926 | To improve security TLS v1.0 and TLS v1.1 are now disabled by default for all back-end components. To change these options, or set a custom cipher suite override the following variables in user_vars.yml: - opsview_tls_versions_disabled - opsview_tls_cipher_suite |
Update: 27 March 2020 (6.3.5)
| ID | Summary |
|---|---|
| OP-37971 | Resolved issues where Downtime was allocated to the incorrect Host/Device |
Update: 06 March 2020 (6.3.4)
| ID | Summary |
|---|---|
| OP-37932 | Resolved data issues within BSM database tables that were affecting the accuracy of BSM Reports |
Update: 08 January 2020 (6.3.2)
| ID | Summary |
|---|---|
| ODI-4849 | Provide support for CacheManager component when TLS is not enabled |
Release: 03 December 2019
This section lists general defects across the product that have been addressed in Opsview Monitor 6.3 release.
Note that any fixes from previous release dates are rolled up into this latest release.
| ID | Summary |
|---|---|
| OP-34793 | Solved rare cases where Datastore shards were filling up the filesystem |
| OP-34807 | Address occurrences where Reload Progress bar doesn't start and hangs on the screen |
| OP-31273 | Now Custom host icons are kept after migration |
| OP-31327 | During an In-place upgrade, rrd data gets migrated |
| OP-34301 | Improved performance for the History tab when retrieving the default 100 results |
| OP-32632 | Fixed issues with inconsistent collection plan generation for SNMP checks |
| OP-25795 | UI Improvement in Autodiscovery for the Exclusion List indicator |
| OP-33062 | syslog is not terminated anymore when logrotate is run |
| OP-34847 | Solved cases where Apply Changes modal window doesn't display Text Strings |
| OP-32589 | Handle passive checks with a "colon-number" (":0") in the check name or plugin output |
| OP-35491 | SSH tunnels from master to collectors successfully recover after collectors go offline and come back online |
| OP-35335 | Fixed issues with Datastore views compaction |
| OP-22579 | Info Tab in the Investigate Window now includes Downtime and Acknowledgement details |
| OP-35908 | Watchdog consistently restarts between RPM and Debian package upgrades without failing |
| OP-35908 | Prevent upgrade errors due to watchdog stopped |
| ODI-3726 | Solved performance issues on Opsview Monitor and ESXi systems, when check_vsphere plugin is provided with incorrect Credentials |
| ODI-2395 | General AWS S3 Opspacks fixes and improvements |
| ODI-3498 | Azure Service Checks improvements for logic on warning and critical thresholds |
| ODI-3939 | Solved Incorrect logic to determine certificates usage for check_vsphere plugin |
Updated almost 3 years ago