What's New?

Discover what's new in this release

What's New (6.7.6)

General Updates

The cursor on Graph Center is now synced to show position and selection at the same time on all on-screen graphs.

The NetAudit code has been hardened to cope with additional illegal characters in configurations fetched from external servers. The existing rancid software already makes some attempts to filter out unwanted characters, and this has been extended within the Opsview NetAudit code.

New Windows and Linux Agent Beta

A new agent for Linux and Windows based machines is now in closed beta. If you are interested in taking part, please reach out to either CS or your account manager.

Network Topology Security

A new Network Topology permission NTVIEWALL has been added which, when applied to a role, allows a user to view any unimported nodes in the network topology map. The NTVIEWALL permission will be applied to all existing roles with both the VIEWALL and CONFIGUREVIEW permissions when upgrading. See Network Topology Visible Hosts for full details.

Also fixed two Network Topology Known Issues to improve security.

New Time Range Presets

The Events Viewer, Notifications and Graph Center pages have access to new preset time durations. These are:

  • last full day - The last full 24 hour period (00:00 to 00:00).
  • last full 7 days - The last 7 full 24 hour periods (00:00 to 00:00).
  • last full week - The last full week e.g. if used on Tuesday, this would be the previous Monday - Sunday.
  • last full month - The last full month e.g. if used on Feb 5th, this would be Jan 1st - Jan 31st.

Dashboard Updates

Added two new Netflow dashlets:

  • Receivers Protocol Trend - Display the top ports and protocols used to receive data, as recorded by the source device (such as a switch or firewall) that supports netflow/sflow.
  • Transmitters Protocol Trend - Display the top ports and protocols used to transmit data, as recorded by the source device (such as a switch or firewall) that supports netflow/sflow.

Added the ability to select historical time ranges (see Dashlet Time Range Picker) to the following dashlets:

Added a new Dashboard Time Range Sync mode to sychronize cursors and zooming across supported dashlets.

Jasper Server Upgrade to 8.1.0

The Reports Module has been updated to use Jasper Server 8.1.0 and Tomcat 9.0.65 which fixes a number of security vulnerabilities. UI and functionality remain the same, however, note two new UI features:

  • Favourite Report selector (home page)
  • Schedule report button/shortcut (edit report view)

Note, following a successful upgrade, email configuration settings will need to be reapplied - see Known Issues.

Flow Collector Improvements

opsview-flow-collector has been made more resilient to any messagequeue failures, so it will now reconnect automatically.

A TTL (time to live) has been added to any flow requests made via the REST API, so messages will be automatically removed if a flow-collector does not pick up the request within 30 seconds. This avoids a build up of messages if the component is stopped temporarily.

Additional timing data will be returned by Flow REST API calls, for debugging:

  • collector - the machine ref for the collector that has run this flow request
  • duration_total - the total time spent running the call on the remote collector
  • duration_nfdump - the time spent by the call running the nfdump command

What's New (6.7.5)

  • Integrated with ITRS Uptrends
  • Deploy enhanced to enable using sudo without the NOPASSWD option
  • Fixed an issue so re-notifications are now consistently sent following configuration changes
  • Multiple security enhancements including:
    • Improving security access related to view access to monitoring servers
    • Implementing a Content Security Policy - if using OAuth2 authentication, additional configuration is now required (see OAuth2 Configuration)
    • Removing the Opsview software version disclosure to unauthenticated users
    • Implementing a session timeout redirection to the login page
    • Switch syncing plugins to collectors from using rsync to internal ansible/deploy commands to reduce the reliance on sudo access

Uptrends Integration

ITRS Uptrends are a leader in website monitoring, web application monitoring and API monitoring. The new 'Cloud - Uptrends' Opspack provides an integration to monitor your Uptrends monitors in Opsview. The following host templates are provided as part of this Opspack:

  • Cloud - Uptrends - Synthetics
  • Cloud - Uptrends - MultiStep API
  • Cloud - Uptrends - Transaction
  • Cloud - Uptrends - Waterfall
  • Cloud - Uptrends - RUM

For more information on Uptrends, visit https://www.uptrends.com/

Deploy Updates

It is now possible to deploy Opsview to collectors using sudo without the NOPASSWD option set. In this case the orchestrator will need to know the local password for this account, so it is advised to turn off remote password login for this account by adding the following to the sshd_config on the collector.

Match User <local user for sudo>
  PasswordAuthentication no

The following playbooks will now set up the appropriate version of python on InfluxDB systems if configured, as the first action in a deployment:

  • check-deploy.yml
  • setup-hosts.yml

Re-notifications are now consistently sent following configuration changes

In previous versions of Opsview Cloud, re-notifications did not consistently take configuration changes into account if an object was in a non-OK state prior to the change. For example, adding a Hashtag with Notifications applied to a Service Check in a non-OK state will now correctly send all notifications.

What's New (6.7.3)

  • Integrated with ITRS Obcerv
  • Updated Rancid to v3.13 enabling us to support the latest network devices within NetAudit
  • Added flapping start/stop notifications
  • Enhanced the Opspack import process to overwrite any existing configuration
  • Improved performance when handling large numbers of passive checks
  • Security
    • Added encryption between components and MySQL server
    • Fixed an issue related to host header injection attempts
    • Stopped sending username/hostname in GET requests from the UI
    • Improved session manager security related to encryption keys

Flapping start/stop notifications

Enabled notification profiles will now get Flapping start/stop notifications if the flapping detection is enabled in the host/service check and flapping notification is enabled in both the profile and the host/service check. Note: flapping stop notifications will NOT be sent during a notification suppression period.

Opspack import --overwrite-variables flag

The /opt/opsview/coreutils/bin/install_opspack utility now supports a new flag, --overwrite-variables, that can be used in conjunction with the existing --force flag. If the --force --overwrite-variables flags are provided, variables defined in the imported Opspack will have their “arg1”, “arg2”, “arg3”, and “arg4” fields set in the configuration database, while respecting the relevant “secured” field. This means if “secured3” is set to 1, then the value for “arg3” will be encrypted and stored in the database appropriately.

For variables defined within the Opspack, if /opt/opsview/coreutils/bin/install_opspack --force is executed without the --overwrite-variables and the variable already exists, then the import will ignore the values of the “argX” and “securedX” fields and will not be overwritten. If the variable does not exist, then the “argX” will be inserted (but “securedX” will still be ignored). This is the previous behaviour and is retained for compatibility.

Note that without the --force flag, the --overwrite-variables flag will have no effect as the utility will not update an existing variable.

When using the new flag, if a variable argument transitions between states of the appropriate “secured” field, the following will happen:

  • If an argument has “securedX” change from 0 to 1, then all host variables with “argX” will become encrypted.
  • If an argument has “securedX” change from 1 to 0, then all host variables with “argX” will be cleared for security reasons. The data that was encrypted will be lost.

Self Monitoring Update

Self monitoring of Opsview Components has been improved with additional Host Templates (see Opspack Changes below). Any new Host Templates that are appropriate for your system will be applied when running the setup-monitoring.yml playbook as part of the post-upgrade process.

Opspack Updates

The following Opspacks have been updated:

  • Opsview - Self Monitoring (v1.3.0)
    • The following Host Templates are now available (Service Check information can be viewed in the Opsview UI):
      • Opsview - Component - Automonitor Manager
      • Opsview - Component - Netaudit
      • Opsview - Component - Reporting Module
      • Opsview - Component - Results Exporter
      • Opsview - Component - Service Desk Connector
      • Opsview - Component - Session Manager
      • Opsview - Component - Web App Server
      • Opsview - Component - Web Server
    • These will be applied as part of running the setup-monitoring.yml playbook if applicable to your Opsview system, except for the “Opsview - Component - Results Exporter” Host Template, which should be manually added as part of the component installation - see Results Exporter Management.

What's New (6.7.1/6.7.0)

Improved upgrade times

Multiple improvements to reduce the upgrade times of Opsview

Opsview Python 3 Upgrade

Opsview Cloud now uses Python 3.9.7 to leverage continuous Python third-party security vulnerability fixes and overall packages improvements for the many Python packages that are used within Opsview Cloud.

We recommend reviewing and updating any custom uploaded Opspacks, monitoring plugins, notification scripts, or event handlers, if they are using the Opsview Python environment, to ensure compatibility with Python 3.9.7 and any libraries provided in the opsview-python3-modules package. A full list of included Python libraries can be found at Opsview Python Libraries.

Opspack updates

The following Opspacks have been updated to support Python 3.9.7, with some additional fixes:

  • Application - Kubernetes (v1.0.5)
  • Application - Microsoft 365 (v2.0.6)
  • Application - Microsoft DNS Agentless (v2.2.1)
  • Application - Microsoft Hyper-V Server Agentless (v2.2.1)
  • Application - Microsoft IIS Agentless (v2.2.1)
  • Application - Microsoft Message Queue Agentless (v2.2.1)
  • Application - Opsview (v3.0.1)
  • Cloud - AWS (v1.0.2)
  • Cloud - Azure (v2.2.4)
    • Fixed issue causing an incorrect error message when using an invalid Azure Tenant ID
  • [BETA] Cloud - Azure - SQL Database Managed Instances (v2.4.5-beta5)
    • Fixed issue causing an incorrect error message when using an invalid Azure Tenant ID
  • Cloud - Azure - Generic (v2.0.2)
  • Cloud - Azure - Internet of Things (v2.1.1)
  • Cloud - GCP (v1.0.4)
  • Cloud - OpenStack (v1.0.4)
  • Database - Microsoft SQL (v2.0.4)
  • Database - Microsoft SQL Database States Agentless (v2.2.1)
  • Database - Microsoft SQL Performance Agentless (v2.2.1)
  • Database - Microsoft SQL System Agentless (v2.2.1)
  • Database - MongoDB (v2.1.2)
  • Infrastructure - Cisco UCS (v1.0.3)
  • Network - Cisco ACI (v1.0.6)
  • Opsview - Component - DataStore (v4.1.1)
  • Opsview - Component - Load Balancer (v4.1.1)
  • Opsview - Component - MessageQueue (v4.1.1)
  • Opsview - Component - Registry (v3.0.1)
  • Opsview - Self Monitoring (v1.1.5)
  • OS - Microsoft Exchange 2013 Backpressure (v2.0.1)
  • OS - Microsoft Exchange 2016 Backpressure (v2.0.1)
  • OS - Microsoft Exchange Counters (v2.0.1)
  • OS - VMware vSphere (v2.0.11)
  • OS - Windows Base Agentless (v2.2.1)
  • OS - WinRM Base Agentless (v2.3.1)

NodeJS Upgrade

Opsview Cloud now uses NodeJS 16.14.0, which has the latest available security fixes. NodeJS modules are also updated to resolve security issues. The list of top level modules used and distributed by Opsview are list at Opsview NodeJS Modules.

Jaspersoft Studio support for Opsview Reporting Module

The Opsview Reporting Module now supports the use of Jaspersoft Studio (v6.11.0 - v6.19.0) for editing and publishing customised reports. Full usage instructions can be found at Creating a Custom Report with Jaspersoft Studio, and troubleshooting tips can be found at Troubleshooting Reports.

Opsview Reporting Module on rehomed systems

Fixed issue preventing the Opsview Reporting Module from displaying on rehomed systems - as described on Rehoming, the Reporting Module will correctly ignore the rehoming and be served under /jasperserver.

Monitoring Plugin updates

The urlize plugin has been removed from Opsview Cloud due to security concerns. By default, no Service Checks use this plugin. However, any custom Service Checks configured to use this plugin will remain in the system, but will begin returning CRITICAL results with no data. We recommend either:

  • preventing these Service Checks from running by removing them from any Host Templates
  • deleting these Service Checks

Both options can be performed via the UI in Configuration > Service Checks .
The negate plugin has been updated with enhanced security.


The Opsview Web App Server component now shows the correct build number in the “My System: System Overview” page.

Defect Fixing

This release also addresses an additional number of general defects across Opsview Cloud. For more details see here.