Before upgrading to Opsview Monitor 6.5
Prior to installing or upgrading Opsview to this version, please read the following pages:
The [**What's New?**](🔗) guides for all versions between the one you are upgrading from up to and including this version,
The [**Prerequisites**](🔗) guide,
The relevant [**New Installation**](🔗) or [**In-Place Upgrade**](🔗) guides
Questions? - Open a Support ticket with our technical team through the [Support Portal](🔗).
Short on resource to perform an upgrade or migration? - Let our technical experts do this for you, followed by a full health check to ensure your environment is running efficiently. Available for a limited time, we are offering significant discounts on assisted upgrades.
For [Major](🔗) and [Minor](🔗) version upgrades, please get in touch with your Account Manager to schedule the upgrade while the offer lasts.
Ubuntu 16 End Of Support Notice
Support for Ubuntu 16 will be removed in Opsview Monitor 6.6 (due early Autumn 2021).
# Support for RHEL8
This release adds RHEL8 to the list of supported Operating Systems.
# Support for MySQL 8.x and MariaDB 10.x
Support has been added for MySQL 8.x and MariaDB 10.x databases for all new installations. Upgraded systems will defer many of the schema changes required which allows you to perform the required additional checks.
The manual schema upgrade _may_ take many hours to run and you need to ensure your database server has adequate disk space available. The schema upgrade does _not_ have to be run at the same time as the Opsview Monitor upgrade, but may be performed at a later date. However, future upgrades may be blocked until this manual schema process is performed. See [MySQL 8 / MariaDB 10 Support](🔗) for more details.
# Improved UTF-8 support
Support for MySQL 8.x and MariaDB 10.x also includes improved UTF-8 support within both the UI and the database (which enabled when the schema migration process is run, as documented in the above section.
# Changes to 'OS Update' handling
Opsview Deploy no longer installs all available OS updates when upgrading Opsview Monitor and conversely, performing OS updates no longer also upgrades Opsview Monitor.
All OS updates should be applied separately to Opsview Monitor upgrades as part of normal SysAdmin duties either by running normal OS package maintenance commands or by running the Opsview Deploy `
We recommend all OS updates are applied before upgrading Opsview Monitor.
# Autodiscovery Improvements (from 6.5.4)
The Autodiscovery network services scanning algorithm has been improved through parallelisation to provide faster scans, and the reported estimated times have been updated to more closely reflect the true values. Users can expect to see more accurate estimations and, depending on the type of scan and detection options set, shorter scan times.
# Support for Ubuntu 20 (from 6.5.4)
This release adds Ubuntu 20.04 to the list of [Supported Operating Systems](🔗).
# FIPS Support (from 6.5.4)
This release add FIPS (Federal Information Processing Standards) support to some operating systems - see [Supported Operating Systems](🔗) for more details.
# Single Sign-On with OAuth2 (from 6.5.4)
This release adds OAuth2 authentication - see [OAuth2](🔗) for more details
# Opspack updates (from 6.5.4)
The following Opspacks have been marked as deprecated:
cloud-aws-s3-cloudwatch (use `
Cloud - AWS` instead)
The following Opspacks have been updated:
Network - Cisco IPSLA (v2.1.0)
General bug fixes and improvements.
Allows monitoring of individual IP SLA operations by ID using the new IP SLA ID argument in the IPSLA host variable. Users with exceptions and timed exceptions on these service checks will need to update their service check arguments to make use of this new argument.
Cloud - Azure (v2.1.0)
General bug fixes and improvements.
Removed unused (but previously required) arguments of “resource-group” and “resource-name” from two Service Checks:
Cloud - Azure - Network Watcher - Connection Monitors
Cloud - Azure - Network Watcher - VM Connectivity
Following an upgrade, these checks should continue to work correctly, but any Hosts that have an `
Exception` or `
Timed Exceptions` set for these Service Checks will report an UNKNOWN state with the following error: usage: check_azure -m MODE [-h] (Optional Arguments) (Mode Specific Flags) check_azure: error: unrecognized arguments: --resource-group --resource-name. To fix this, simply remove the two arguments wherever they appear in the Exception or Timed Exceptions.
Additionally, if the Host Templates containing these Checks (of the same name) have been modified to include Exceptions or Timed Exceptions, these will encounter the same problem and require the same fix.
[BETA] Cloud - Azure - SQL Database Managed Instances (v2.4.2-beta5)
Minor error message improvements.
# Defect Fixing
This release also addresses an additional number of general defects across Opsview Monitor. For more details see [here](🔗).