What's New?

Before upgrading to Opsview Monitor 6.6
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.
# Windows DCOM Hardening / RHEL 7 Support for WMI Opspacks (from 6.6.7)
Our WMI-based Windows Opspacks have been updated to run correctly on RHEL 7 collectors, and to support servers with Windows DCOM Hardening enabled. Includes:
Application - Microsoft Hyper-V Agentless v2.2.2
Database - Microsoft SQL v2.0.3
OS - Windows WMI - Base Agentless v2.1.2
OS - Windows WMI - DNS Agentless v2.1.2
OS - Windows WMI - IIS Server Agentless v2.1.2
OS - Windows WMI - Terminal Services Agentless v2.1.2
# SNMPv3 AES256 and AES256c Privacy Protocol Support (from 6.6.7)
When setting up SNMP monitoring on a Host (either manually or through Autodiscovery SNMP agent detection) using SNMPv3, the ‘aes256’ and ‘aes256c’ privacy protocols are now available. However, custom SNMP Polling Service Checks and SNMP Traps only support these new privacy protocols when run/received on RHEL 8 systems (see [SNMP Privacy Protocol Support](🔗﻿)).
Network Topology detection does not yet support these new privacy protocols, and will ignore Hosts configured with them.
# Network Topology (included in 6.6.3) (updated in 6.6.6)
The Network Analyzer module has now been enhanced with Network Topology. More information can be found [here](🔗﻿)﻿
From version 6.6.6, this includes real-time status overlays in the maps.
# vSphere 7.0 support (from 6.6.6)
Added support for monitoring of vSphere 7.0 based systems.
# Support for Debian 8 is now deprecated (from 6.6.4)
See the complete list at [Supported Operating Systems](🔗﻿)﻿
# Support for Debian 10
This release adds Debian 10 to the list of [Supported Operating Systems](🔗﻿).
# Microsoft Teams Integration
Enables teams to collaborate within MS Teams when an alert is raised ensuring that the right alert goes to the right person, at the right time, for the right reason​. For more details, see [here](🔗﻿) and [here](🔗﻿)﻿
# Security Enhancements
Fixed a SQL Injection vulnerability
NGINX has been upgraded to the latest stable version
Autocomplete is disabled on sensitive forms
SameSite attribute on cookies is now set to strict across most of the product
**(Included in 6.6.3)**
AuthTKT is no longer used by Opsview Monitor to manage user sessions. The Opsview Session Manager now deals with the creation and expiration of sessions for Opsview Monitor.
Opsview Deploy variable `opsview_auth_tkt_ignore_ip` has been deprecated and replaced with `opsview_session_ignore_ip`.
Existing values of `opsview_auth_tkt_ignore_ip` will continue to be used if the new `opsview_session_ignore_ip` variable is not set.
If both are set, `opsview_session_ignore_ip` takes precedence. 
Angular has now been upgraded to the latest version
Removed the version identification of easyxdm
**(Included in 6.6.5)**
To mitigate [CVE-2021-44228](🔗﻿), [CVE-2021-45105](🔗﻿) and [CVE-2021-45046](🔗﻿) (Log4shell vulnerabilities), the Log4j library used within the Opsview Reporting Module has been upgraded to an unaffected version.
**(Included in 6.6.6)**
Fixes for the recent [Apache Log4Shell Vulnerabilities](🔗﻿) 
Fix for remote code execution vulnerability in NetAudit. This only impacts users on v6.5 and v6.6. See [Fixed Defects](🔗﻿) for more details
# Opsview Deploy Updates (included in 6.6.5)
The pre-requisite of having Python 2 installed on all servers prior to deployment has been removed. Now, `opsview-deploy` will set up the appropriate version of python on the system as the first action in a deployment. Note that we do not support running multiple playbooks via `opsview-deploy` at the same time - they should be run as instructed from the examples on Knowledge Center. Updated playbooks:
`check-deploy.yml`
`setup-hosts.yml`
# Opspack Updates
**Application - Microsoft 365 (v2.0.5) - (included in 6.6.7)**
Due to the deprecation of the Office 365 Service Communications API, our Microsoft 365 offering has been updated to use the Microsoft Graph API for all service checks.
The Microsoft Azure application used for these host templates will need to have the following permissions (Application and Delegated):
Microsoft Graph
`Reports.Read.All` - Read all usage reports
`SecurityEvents.Read.All` - Read your organization's security events
`ServiceHealth.Read.All` - Read service health (* _new for this release_)
Previous versions of the Opspack (v2.0.4 and earlier) used the following permissions. These are no longer required and can be removed from the application:
Office 365 Management APIs
Read activity data for your organization
Read service health information for your organization
Full updated documentation for this Opspack can be viewed at [Microsoft 365 Monitoring](🔗﻿).
**Application - Microsoft Hyper-V Agentless (v2.2.2) - (included in 6.6.7)**
Added support for servers with Windows DCOM Hardening.
Now runs correctly from RHEL 7 collectors.
**Azure - Generic**
Improved documentation for the “Azure - Generic” Host Template to improve ease of use when setting up custom Azure monitoring. New documentation can be viewed at [Opsview Azure Custom Monitoring](🔗﻿).
**Cloud - Azure (v2.1.1)**
Fixed timestamp parsing bug affecting the following Service Checks:
Azure - Windows VM - Shutdowns
Azure - Windows VM - Restarts
Azure - Linux VM - Shutdowns
Azure - Linux VM - Restarts
**Cloud - Azure (v2.2.1)**
Due to changes to the Network Watcher Connection Monitor resources available in Azure, our Connection Monitor offering has been updated to highlight our continued support for the “Classic” Connection Monitors:
The “Cloud - Azure - Network Watcher - Connection Monitors” Host Template has been renamed “Cloud - Azure - Network Watcher - Classic Connection Monitors”.
The “Cloud - Azure - Network Watcher - Connection Monitors” Service Group has been renamed “Cloud - Azure - Network Watcher - Classic Connection Monitors”.
The “Azure - Network Watcher - Connection Monitors” Service Check has been renamed “Azure - Network Watcher - Classic Connection Monitors”:
This name change will clear the check execution history for this specific check only, so if maintaining this record is desired, export the historical data before upgrading ([Service Check - Investigate](🔗﻿)).
Any dashlets, reports or filters that have been configured to use the original Service Check name will need to be manually modified to use the new name.
**Cloud - Azure (v2.2.2) - (included in 6.6.1)**
Fixed bug causing the following Service Checks to return an UNKNOWN status with no message, they will now return data from Azure Elastic Pool resources correctly:
Azure - EP - Allocated Storage
Azure - EP - Allocated Storage Percent
Azure - EP - CPU Usage
Azure - EP - CPU Used
Azure - EP - Data IO Percent
Azure - EP - eDTU Used
Azure - EP - Log IO Percent
Azure - EP - Process CPU Usage
Azure - EP - Process Memory Usage
Azure - EP - Sessions Percent
Azure - EP - Storage Usage
Azure - EP - Storage Used
Azure - EP - Tempdb Percent
Azure - EP - Workers Percent
Azure - EP - XTP Storage Percent
Additionally, now all Service Checks within the “Cloud - Azure - Elastic Pool” Host Template will assume a default Elastic Pool type of ‘DTU’, if none is provided.
**Database - Microsoft SQL (v2.0.3) - (included in 6.6.7)**
Added support for servers with Windows DCOM Hardening.
Now runs correctly from RHEL 7 collectors.
**OS - VMware vSphere (v2.0.8) - (included in 6.6.1)**
Updated the order of results when items are degraded, so that they are listed in order of severity: CRITICAL, WARNING, UNKNOWN, OK. Affected Service Checks:
vSphere - Host - VM Status
vSphere - Host - Datastore Usage
vSphere - Host - Datastore Used
vSphere - Host - Datastore Latency
vSphere - Host - Datastore VM Observed Latency
vSphere - Host - Datastore Read/Write
vSphere - Guest - Datastore Usage
vSphere - Guest - Datastore Used
vSphere - Guest - Datastore Latency
vSphere - Guest - Datastore Read/Write
For the "vSphere - Host - Network Adapters" Service Check, updated the order of results when items are degraded, so that they are listed in order: DOWN, UP.
For the "vSphere - Host - NIC Summary" Service Check, updated the order of results when items are degraded, so that they are listed in order: DOWN, DOWN (EXPECTED), UP.
For the "vSphere - Host - Port Group Summary" Service Check, updated the order of results when items are degraded, so that they are listed in order: DOWN, UP, no network association.
For the "vSphere - Host - Temperature" Service Check, updated the order of results when items are degraded, so that they are listed in order: Alert (RED, GRAY or YELLOW), non-alert (GREEN).
**OS - VMware vSphere (v2.0.9) - (included in 6.6.3)**
Updated the order of results when items are degraded, so that they are listed in order of severity: CRITICAL, WARNING, UNKNOWN, OK. Affected Service Checks:
vSphere - vCenter - Backup Status
vSphere - vCenter - Cluster Status
vSphere - vCenter - CPU Usage
vSphere - vCenter - Datastore Status
vSphere - vCenter - DNS Status
vSphere - vCenter - Filesystem Status
vSphere - vCenter - Health Status
vSphere - vCenter - Host Status
vSphere - vCenter - Memory Usage
vSphere - vCenter - NIC Status
vSphere - vCenter - NTP Status
vSphere - vCenter - Proxy Server Status
vSphere - vCenter - Service Status
vSphere - vCenter - Swap Usage
vSphere - vCenter - Time Synchronisation
vSphere - vCenter - Updates
vSphere - vCenter - Uptime
vSphere - vCenter - VCHA Cluster Status
vSphere - vCenter - Version
vSphere - vCenter - Virtual Machine Status
**OS - VMware vSphere (v2.0.9) - (included in 6.6.6)**
Added support for vSphere ESXi 7.0 and vCenter 7.0.
The behaviour of the "vSphere - Host - Health Issues" and "vSphere - Host - Temperature" Service Checks has been updated - they will now report an UNKNOWN status when no data is found on the target ESXi Host.
The "vSphere - vCenter - NTP Status" Service Check will now report an UNKNOWN status if no NTP servers have been configured on the target VCSA.
**OS - Windows WMI - Base Agentless (v2.1.2) - (included in 6.6.7)**
Added support for servers with Windows DCOM Hardening.
Now runs correctly from RHEL 7 collectors.
**OS - Windows WMI - DNS Agentless (v2.1.2) - (included in 6.6.7)**
Added support for servers with Windows DCOM Hardening.
Now runs correctly from RHEL 7 collectors.
**OS - Windows WMI - IIS Server Agentless (v2.1.2) - (included in 6.6.7)**
Added support for servers with Windows DCOM Hardening.
Now runs correctly from RHEL 7 collectors.
**OS - Windows WMI - Terminal Services Agentless (v2.1.2) - (included in 6.6.7)**
Added support for servers with Windows DCOM Hardening.
Now runs correctly from RHEL 7 collectors.
**SNMP - MIB II (v4.1.1) - (included in 6.6.7)**
Now supports the 'aes256' and 'aes256c' SNMPv3 privacy protocol options.
**Azure - Generic**
Improved documentation for the “Azure - Generic” Host Template to improve ease of use when setting up custom Azure monitoring. New documentation can be viewed at [Opsview Azure Custom Monitoring](🔗﻿).
# Defect Fixing
This release also addresses an additional number of general defects across Opsview Monitor. For more details see [here](🔗﻿).
Deprecation Updates
Ubuntu 16 is no longer a supported Operating System in Opsview 6.6
Debian 8 is no longer a supported Operating System after Opsview 6.6.3