Opsview 6.x Release Notes
Opsview release notes contain the list of enhancements of features, and a set of issues fixed in the currently supported versions of Opsview Monitor. Note that any fixes from previous release dates are rolled up into the latest release. For more information, see Support Policy.
Before you install Opsview, make sure to check the 6.x Compatibility Matrix. For details on installation, administration, and usage, you may refer to Opsview Monitor documentation. For the latest highlights, see What’s New in Opsview.
Archived release notes for Opsview 6.9.x and earlier versions are available at Opsview 6.9.x Release Notes. For legacy release notes of Opsview 6.7.x and earlier, refer to the Opsview Knowledge Center.
Opsview 6.12.0 Copied
Released: 25 February 2026
Highlights Copied
These are the highlights of this release:
- Optimized the
GET /rest/statusand related endpoints to reduce database load and minimize temporary table creation on disk. This improves the responsiveness of host and service status views, especially in large environments with high monitoring volumes. - Fixed an issue where the vCenter - Datastore Status Check incorrectly reported the same usage metrics for each datastore in vCenter v7 and v8 when using multiple service checks. You now have accurate, granular visibility of storage capacity without additional configuration.
- Updated the default JavaScript export timeout to 600 seconds to align with nginx timeout settings. This prevents UI timeouts during large host exports and ensures customers can reliably export large configurations directly from the web interface.
- Increased the NetAudit FastCGI timeout to 180 seconds and made it configurable. This prevents timeouts when listing large rancid repositories in NetAudit environments with thousands of devices, improving reliability for large-scale deployments.
- Improved session timeout handling when accessing Opsview through a proxy server by preventing caching of the
idle-timeout.jsonfile. The UI now always retrieves the current timeout configuration from the server, ensuring that any session timeout changes are applied consistently and reliably for users behind proxies. - End-of-life (EOL) notice for operating system support
- Ubuntu 20.04 support was introduced in the Opsview 6.10.1 release, and Ubuntu 20.04 has now reached its End-of-Life (EOL) state.
- As a result, Opsview versions 6.12.0 and later cannot be deployed on Ubuntu 20.04. While we will continue to support existing Opsview versions according to our support policy, we strongly recommend migrating to an actively supported operating system. Since Ubuntu 20.04 will no longer receive security updates, prioritizing system security is crucial.
- End of support notice for Opsview 6.9.x
- With the release of Opsview 6.12.0, versions 6.9.x have reached their End-of-Support (EOS) status according to our support policy. This means that versions 6.9.x will no longer receive code fixes or security updates.
- The documentation for version 6.9.7 and earlier versions will remain accessible for the time being, but it will no longer be updated or receive backports. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.
- This release deploys the Opsview repository version
6.12.0.202602232338. - This release deploys the Infrastructure Agent version 2.10.11138 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-75939 | Improved performance of the /rest/status endpoint for faster and more efficient system status responses. |
| OP-75952 | Increased the NetAudit page timeout to 180 seconds, with a configurable deploy setting for large repository operations. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-74711 | Fixed an issue where the vCenter Service Check displayed incorrect datastore values for vCenter Server versions 7 and 8. |
| OP-75156 | Aligned timeout for exporting Hosts from the UI with NGINX timeout settings to ensure consistent request handling. Timeout is now set at 600 seconds. |
| OP-75909 | Fixed an issue where the scheduler failed to parse collection plans when the system timezone was invalid. |
| OP-75953 | Fixed an issue that prevented downtime scheduling at the Service Check level. |
| OP-75978 | Fixed session timeout issues by ensuring the idle-timeout.json file is not cached. The fix adds a Cache-Control: no-cache header to the response, allowing the UI to respect the configured session idle timeout correctly. |
| OP-75983 | Fixed an issue where users who previously had access to the old downtime page were unable to access the new downtime page due to permissions settings. Access is now correctly aligned with user roles. |
Opsview 6.11.7 Copied
Released: 18 December 2025
Highlights Copied
These are the highlights of this release:
- A new State Manager has been added to Cache Manager to provide persistent, cluster-wide storage of JSON data with configurable time-to-live (TTL), accessible from any collector node via simple APIs. This data now survives reboots, supports store and fetch operations, and ensures the most recent version is retained using timestamps. This enables you to create more reliable and stateful plugins, allowing advanced monitoring logic that depends on shared, durable state across the cluster.
- The Scheduled Downtime page now includes a dedicated search bar, multi-row selection, and per-object selection to edit or cancel downtime. These changes give you more precise control over downtime, helping you reduce risk, avoid accidental changes, and manage complex environments with greater confidence and accuracy.
- The Schedule Downtime modal has been updated with a new tabbed layout that preserves the existing status-based selection while introducing a General Selection tab for filtering and manually selecting hosts and service checks. This makes it easier to target specific objects, especially in large environments, without hitting selection limits, giving you more flexibility and control when scheduling downtime.
- Notice of update in database support policy
- As MySQL 8.0 will reach End-of-Life (EOL) in April 2026, the Opsview database support policy has been updated to include a newer MySQL version.
- Starting with Opsview 6.11.7, MySQL 8.4 is now supported on the following operating systems:
- Ubuntu 22 as the default database
- RHEL 8 and 9 as the non-default database
- OL 8 and 9 as the non-default database
- Ubuntu 20.04 has reached EOL and continues to provide MySQL 8.0 as its final long-term support (LTS) release. Therefore, MySQL 8.0 remains the default database only for Ubuntu 20.04.
- Only the databases listed as the default or non-default choice for a particular OS in our policy are supported. We strongly recommend switching to MySQL 8.4 after upgrading Opsview if you are currently using MySQL 8.0. Instructions are available at Upgrading to MySQL 8.4.
- End-of-Life (EOL) notice for operating system support
- Ubuntu 20.04 reached End-of-Life (EOL) in May 2025. As a result, Opsview 6.12.0 and above (released from February 2026) cannot be deployed on Ubuntu 20.04. Existing Opsview installations on Ubuntu 20.04 will continue to be supported according to the Opsview support policy.
- Since Ubuntu 20.04 no longer receives security updates, we strongly recommend migrating to a currently supported operating system to ensure security, stability, and compatibility with future Opsview releases.
- This release deploys the Opsview repository version
6.11.7.202512171722. - This release deploys the Infrastructure Agent version 2.9.08072 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-29766 | Improved scheduled downtime functionality by allowing you to cancel specific or multiple downtimes by object, providing greater control and flexibility. Enabled access to the redesigned scheduled downtime page, allowing you to take advantage of the updated interface and its enhanced features. For more information, see Viewing and canceling downtimes. |
| OP-74785 | Added support for MySQL 8.4 as a database option: MySQL 8.4 is now supported as a non-default database on RHEL 8 and 9, OL 8 and 9, and Debian 12. For Ubuntu 22, MySQL 8.4 is now the default database. Ubuntu 20 will continue to use MySQL 8.0 as the default. For more information, see the following documentation: |
| OP-75149 | Introduced the Opsview State Manager and persistent datastore support. This release adds a distributed, persistent key-value datastore that can be accessed via plugnpy and Cache Manager. Data persists across restarts and reboots, is shared across all Cache Manager instances in a cluster, supports JSON data up to 16 KB, and is automatically compacted. The new Opsview State Manager is designed for long-lived and session data, complementing Cache Manager, which remains focused on short-term, ephemeral data. |
| OP-75232 | Redesigned the Schedule Downtime modal by introducing a new tabbed interface with Status Based and General Selection panels while preserving existing functionality. It adds manual host and service check selection with sorting, searching, and deletion, dynamically populates Host and Service Check selectors based on the selected Host Group, Host, or Hashtag, and includes adaptive Add Hosts and Add Service Checks buttons that automatically enable or disable as appropriate. |
Opsview 6.11.6 Copied
Released: 29 October 2025
Package rebuilds with updated checksums
The following packages were rebuilt as part of the Opsview 6.11.6 release without any functional or code changes. Due to the rebuild, their checksums have changed, which may cause them to appear as available for upgrade in some environments.
Affected packages:
opsview-erlangopsview-krb5opsview-nodejsopsview-pkiopsview-powershellopsview-python3opsview-setupopsview-web-app-ui-externalopsview-web-app-ui-themeThis is a non-impacting change, and no action is required unless checksum consistency is strictly enforced in your deployment processes.
Highlights Copied
These are the highlights of this release:
- Support for exporting parent and child host lists has been added to Results Exporter. This enhancement enables integration scenarios such as ITSM configurations that rely on host hierarchies, for example, preventing ticket creation for child hosts when a parent host is down.
- Introduced the
pre_filter_custom_fieldssetting in the Results Exporter for file, syslog, and HTTP outputs, enabling more flexible data routing and integration based on enriched host or service metadata. - Optimization of the
/rest/eventAPI has been implemented by introducing a threshold mechanism to determine when to use straight joins for large event queries. This improvement significantly enhances response times and reduces database load for event-related dashboards and views. - This release contains security fixes.
- This release deploys the Opsview repository version
6.11.6.202510271635. - This release deploys the Infrastructure Agent version 2.9.07110 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-51302 | Optimized the /rest/event API to improve performance for large event queries by introducing a threshold-based mechanism for using straight joins, resulting in faster response times and reduced database load for event-related dashboards and views. |
| OP-57584 | Introduced the pre_filter_custom_fields setting in the Results Exporter for file, syslog, and HTTP outputs, allowing string custom fields to be added to messages before filtering for use in filter expressions. This release also enhances support for YAML multiline strings when defining filters. |
| OP-75379 | Added two new fields, parent_host_names and child_host_names, to the RuntimeHosts model in the Results Exporter. These fields return sorted lists of parent and child host names, respectively, and can be used to enrich exported messages. If no parent or child hosts are defined, the fields return empty lists. |
Opsview 6.11.5 Copied
Released: 23 September 2025
Highlights Copied
These are the highlights of this release:
- The
check_wmi_plusplugin now produces consistently formatted output with correct semicolons and spacing. This ensures results are graphed accurately while making the human-readable output clearer. You can now rely on cleaner, more consistent results for monitoring, with improved graph accuracy and better readability in dashboards and reports. - The Microsoft Hyper-V Agentless Opspack now uses check-Hyper-V.ini version 2, enabling monitoring of Windows Server 2012 and later. This expands compatibility and ensures you have visibility for modern Windows Server environments.
- Opsview now supports hiding the local login interface when SSO is configured, showing only the SSO login option. This ensures all users authenticate through a single, secure method, improving security and accountability.
- This release deploys the Opsview repository version
6.11.5.202509180320. - This release deploys the Infrastructure Agent version 2.8.05102 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-74334 | Improved handling of local login when Single Sign-On (SSO) is configured in Opsview. This update also introduced a new user variable, To improve security and prevent misconfiguration, deployment-time validations were added to:
|
| OP-75171 | The Microsoft Hyper-V Agentless Opspack now uses check-Hyper-V-v2.ini (which relies on root/virtualization/v2) instead of check-Hyper-V.ini. This change enables compatibility with Windows Server 2012 and later versions, as they ship with root/virtualization/v2. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-45287 | Servicedesk Connector now operates efficiently without progressively consuming more memory, ensuring consistent performance and timely operation during normal use. |
| OP-68436 | Fixed an issue where the Apply Changes process could fail when encountering metric names or units of measurement (UOM) that exceed allowed lengths. Also, service check results containing overly long metric names or UOMs are now rejected gracefully. |
| OP-73254 | WMI Plus checkcpu now reports CPU usage correctly. |
| OP-73659 | Fixed an issue where the Ansible template module experienced significant delays when run remotely, which impacted upgrade processing time. The upgrade process has been optimized by caching the data required to generate configurations for generic components once per host. This eliminates redundant data loading for each component and significantly reduces upgrade time when multiple components and hosts are involved. |
| OP-74322 | Fixed an inconsistency between the inventory and Also, the |
| OP-74812 | Fixed an issue where graphing data for service checks using warning thresholds was not being recorded in check_wmi_plus. Graph data is now correctly captured when warning thresholds are applied. |
| OP-75069 | Service checks now correctly handle metric results even when they exceed 100. |
Opsview 6.11.4 Copied
Released: 6 August 2025
Highlights Copied
These are the highlights of this release:
- The Results Forwarder now supports receiving passive check results from the ITRS Infrastructure Agent or other Opsview systems over HTTP. The Results Exporter can also be configured to send results directly to a Results Forwarder.
- Improved the
checkfolderagecommand in thecheck_wmi_plusPython plugin to handle large file volumes, enabling faster folder monitoring even with thousands of files. - Updated scheduled service check behavior to use an empty value when variable arguments are overridden but left empty, matching the behavior when using the Troubleshooting mechanism. Previously, these checks would default to the global variable configuration. This ensures consistency and predictability of your service checks, reducing the risk of incorrect or unexpected service check behavior.
- This release contains security fixes.
- This release deploys the Opsview repository version
6.11.4.202508041400. - This release deploys the Infrastructure Agent version 2.8.05102 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-74642 | Opsview now supports newer versions of the ITRS Analytics Platform and apps for Dynamic Thresholds. For more information, see Dynamic Thresholds. |
| OP-74145 | The Results Forwarder now supports receiving passive check results over HTTP from configured systems, such as the Infrastructure Agent and Results Exporter. This enables results from scheduled plugin executions and cross-system forwarding to be submitted directly to the HTTP Receiver, removing the need for the deprecated Opsview NSCA component. For more information, see Results Forwarder. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-59509 | Empty host variables are now correctly handled during scheduled checks. Previously, this only worked via Troubleshoot, and scheduled executions defaulted to global values. |
| OP-74626 | Fixed an issue where service checks incorrectly entered an UNKNOWN - Stale state at the start of a time period when the Opsview system timezone was set to east of UTC. Staleness of checks is now evaluated correctly across all timezones. |
| OP-74709 | Fixed performance issues in the check_wmi_plus Python plugin when running checkfolderfileage. Previously, the check ran slowly on directories with many files due to inefficient output processing. This has now been improved to reduce execution time. |
Opsview 6.11.3 Copied
Released: 25 June 2025
Highlights Copied
These are the highlights of this release:
- The
check_snmp_fsutilplugin has been updated to check all relevant filesystems while excluding read-only filesystems. This ensures proper monitoring of all filesystems on your host. - The
checkfolderfileagequery in thecheck_wmi_plusPython plugin can now correctly convert forward slashes in the file path to backslashes using theslashconversionargument. This allows you to use the plugin with Linux-style file paths. - The
check_wmi_plusPython plugin can now filter by both service name and startup type, enabling improved selection of the services you want to monitor. - This release contains security fixes.
- This release deploys the Opsview repository version
6.11.3.202506231411. - This release deploys the Infrastructure Agent version 2.7.04081 for self-monitoring.
Note
If you are using Opsview with the Infrastructure Agent on monitored Windows systems, please note that the file type, download location, and installation steps have changed in the latest version. For more details, refer to the Infrastructure Agent 2.7.x. Release Notes.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-74543 | In the vSphere - Host - Datastore Latency service check, a new label message has been introduced for datastores with empty read and write latency due to zero disk capacity: Latency not available, empty capacity. When disk capacity exists but metrics are unavailable, the system will continue to display Unable to extract values. Additionally, the datastore type is now appended in the error messages to help with troubleshooting. For more information, see Host Template: OS - VMware vSphere ESXi Host. |
| OP-73786 | Opsview now supports newer versions of the ITRS Analytics Platform and apps for Dynamic Thresholds. For more information, see Dynamic Thresholds. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-44329 | The check_snmp_fsutil plugin now correctly monitors all relevant filesystems. Additional Linux read-only filesystems are excluded, ensuring accurate monitoring results. |
| OP-73798 | Fixed an issue where the checkfolderfileage query in the check_wmi_plus Python plugin incorrectly handled forward slashes in file paths. Now, the query converts forward slashes to backslashes using the slashconversion argument. |
| OP-73879 | The check_wmi_plus Python plugin has been updated to correctly apply the StartMode filter when using the -4 argument with -a ServiceName filter in checkservice mode. |
| OP-74388 | Fixed an issue where the orchestrator was incorrectly flagged as offline when no system health issues were present. |
Opsview 6.11.2 Copied
Released: 21 May 2025
Highlights Copied
These are the highlights of this release:
- SHA-224 and higher authentication protocols are now supported in Opsview for SNMP polling, SNMP interfaces, SNMP plugins, and SNMP traps. These protocols provide more secure options for SNMPv3 authentication.
- The Performance Graph, Performance Gauge, Metric Pie Chart, Process Map, and Top Services by Metric dashlets have been updated to improve responsiveness when configuring hosts, services, and metrics in large-scale systems.
- Monitoring has been added for the Orchestrator cluster’s messagequeue. If issues are detected, a cluster health alarm will appear on the Collector Management page. This ensures you are promptly alerted to potential problems and can respond in a timely manner.
- Deleted documents in Opsview databases are now automatically removed from the system, improving performance and memory efficiency.
- This release contains security fixes.
- This release deploys the Opsview repository version
6.11.2.202505191726. - This release deploys the Infrastructure Agent version 2.6.03251 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-54491 | Opsview now supports the following SNMPv3 authentication protocol options:
|
| OP-73297 | The id field in the opsview.auditlogs table has been updated from int to unsigned int, doubling its maximum value. This addresses the risk of the audit log id reaching its previous limit due to frequent passive check submissions via the REST API. For high-frequency checks, we recommended using the Results Forwarder to help avoid inflating audit log entries. |
| OP-73579 | Added new monitoring with cluster health alarm for messagequeue issues such as network partitions and memory throttling on the orchestrator. The Configuration > Collector Management page has been updated to show these issues in tooltips, helping you track the health of your master RabbitMQ cluster even if the standard self-monitoring checks are not running. For more information, see Cluster Health Alarms. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-37229 | Opsview can now handle cleanup tasks for flow collector data using a scheduled cron job. Previously, netflow data had no defined retention period, which caused the file system to become full. For more information, see Flow collector housekeeping. |
| OP-43922 | The housekeeping job for the runtime database now works successfully regardless of the number of messages being processed by results-live and results-recent. |
| OP-57486 | Fixed an issue where service checks were immediately marked as stale upon entering their scheduled check period following a monitoring suspension. The Freshness Checker has been updated to include a check interval to the freshness timeout, preventing false alerts by allowing checks sufficient time to run before being evaluated for staleness. For more information, see Freshness Checking. |
| OP-63516 | Deleted documents in the opsview-logs and opsview-sessionmanager databases can now be automatically removed from the system, improving database performance and efficiency. |
| OP-73132 | Fixed a race condition where Apply Changes failed if the system attempted to stop a task that had already completed. |
| OP-73133 | Fixed argument parsing issues in check_dns. Now, the plugin works successfully using standard input (stdin) or command line arguments. |
| OP-73646 | Fixed an issue where uploaded notification scripts could fail to run when executed during metadata file creation. |
| OP-73735 | Fixed performance issues in the configuration windows of the following dashlets:
|
| OP-73820 | The executor agent client (the current built-in check_nrpe plugin) has been updated to function similarly to the check_nrpe plugin from Opsview versions prior to 6.9.2. Previously, when a connection to the agent was refused, an UNKNOWN was returned. Now, the plugin returns a CRITICAL status. The new --unknown-connection-refused plugin option is available to return UNKNOWN in these situations instead; this only works once the whole system, including collectors, has been upgraded. |
| OP-73833 | Fixed an issue in the opsview.reload_stages table where the current_stage value could exceed the max_stages value, which resulted to a disproportionate progress in the reload bar. |
Opsview 6.11.1 Copied
Released: 3 April 2025
Highlights Copied
These are the highlights of this release:
-
ITRS Analytics integration with Opsview Enterprise
- Results Exporter now integrates with ITRS Analytics version 2.x APIs. As a result, Opsview now supports newer versions of the ITRS Analytics Platform and Apps for Dynamic Thresholds. This improves the compatibility of Opsview with ITRS Analytics for easier deployment. For more information, see Configuring Dynamic Thresholds.
- Opsview now enforces data constraints via Results Exporter when ITRS Analytics is used. This prevents silent data loss due to restrictions on datapoints in ITRS Analytics and ensures that supported Opsview data can be properly exported to ITRS Analytics.
-
Cluster Health alarms for degraded clusters are now correctly shown in tooltips on the Collector Management page. This helps you identify and troubleshoot any issues with your clusters.
-
The
opsview-messagequeueself-monitoring has been updated to detect network partitions and monitor memory usage against a configured watermark. This helps you track the health of your RabbitMQ clusters. -
When using an SSO provider with Opsview, alternative webserver addresses are now supported correctly. This allows you to use more readable and appropriate URLs for your Opsview system.
-
The
check_wmi_plusplugin now displays the correct help text in the Plugin Help. This update provides you with better guidance for using the plugin. -
The
check_wmi_plus.plPerl plugin has been deprecated. If you are using this plugin, we recommend updating your service checks to use thecheck_wmi_plusPython plugin instead. The Python version offers improved security and ongoing support. -
Notice of update in database support policy
- With MariaDB 10.3 in End-of-Life (EOL) status and MariaDB 10.5 reaching EOL by June 2025, there is a need to support higher versions of MariaDB in the database support policy.
- Starting with Opsview 6.11.1, MariaDB 10.11 is now supported for the following operating system versions:
- RHEL 8.10 and RHEL 9.4 and above as the default database
- OL 8 and 9 as the default database
- Ubuntu 20 and 22 as the non-default database
- Earlier versions of RHEL 8 and 9 will continue to support MariaDB 10.3 and 10.5, respectively, as default databases. However, we strongly recommend upgrading to the latest RHEL 8 and 9 versions for improved security.
-
This release contains security fixes.
-
This release deploys the Opsview repository version
6.11.1.202504020751. -
This release deploys the Infrastructure Agent version 2.5.01984 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-73311 | Results Exporter has been updated to use ITRS Analytics version 2.x APIs. As a result, the following versions of the ITRS Analytics Platform are now compatible with Dynamic Thresholds in Opsview:
|
| OP-72846 | References to obcerv in the Dynamic Thresholds and Results Exporter documentation have been updated to use analytics for configuration. We recommend updating your configuration to prevent component issues in the future. For more information, see Configuring Dynamic Thresholds. |
| OP-72236 | MariaDB 10.11 is now supported as the non-default database option for Opsview deployments on Ubuntu 20 and 22. For more information, see Supported databases. |
| OP-72235 | MariaDB 10.11 is now supported as the default database in Opsview for RHEL 9.4 and OL 9. For more information, see Supported databases. |
| OP-72234 | MariaDB 10.11 is now supported as the default database in Opsview for RHEL 8.10 and OL 8. For more information, see Supported databases. |
| OP-72149 | The opsviewd component has been removed from Opsview Monitor. Its functionality has been re-implemented in the Orchestrator’s REST API. |
| OP-71025 | The The following Opsview-provided Opspacks might be affected if the system has been deployed before Opsview version 6.9.2:
The |
| OP-61973 | Automatically deployed self-monitoring hosts in Opsview now monitor two new checks against
These use two new modes of the built-in
|
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-73168 | JasperServer’s Spring and Tomcat libraries have been updated to address security vulnerabilities. For more information, see Reporting Module. |
| OP-72417 | The check_wmi_plus plugin now displays the correct help text in the Plugin Help. |
| OP-70516 | When configured to export data to ITRS Analytics, Results Exporter now detects and reports data that violates constraints in ITRS Analytics before sending it. This helps prevent silent data loss. Additionally, the |
| OP-64283 | Fixed an issue when using an SSO provider with Opsview, alongside configured alternative webserver addresses. Now, alternative addresses correctly support the sign-on functionality. |
| OP-63072 | Go Language has been upgraded from 1.19.3 to 1.23.5 to address security vulnerabilities. For more details, see Software Components. |
| OP-44366 | Fixed an issue in the Database - Microsoft SQL Opspack where a misspelling appeared in the Microsoft SQL - Active Transactions service check. |
| OP-61973 | Cluster Health alarms for degraded clusters are now correctly shown in tooltips on the Configuration > Collector Management page. For more information, see Cluster Health Alarms. |
Opsview 6.11.0 Copied
Released: 26 February 2025
Highlights Copied
These are the highlights of this release:
-
Plugin improvements
- The
check_wmi_plusplugin has been updated to handle empty results when the-4option is used. - The
check_vsphereplugin can now handle vCenter clusters and datastores with names containing spaces via vCenter v7 and v8.
- The
-
Remotely managed collector upgrades now support cluster names that contain the literal string
opsview clusteroropsview_cluster. -
The pyopsview REST API client can now be used with multiple Opsview systems simultaneously.
-
AutoMonitor Express Scan has been updated to automatically remove any invalid characters from host and host group names.
-
The Status Objects tab has been updated to use itemselectors when choosing host groups, service groups, and hashtags for a role.
-
Notice of update in database support policy
- With MariaDB 10.3 already in End-of-Life (EOL) status and MariaDB 10.5 reaching EOL by June 2025, there is a need to support higher versions of MariaDB in the database support policy.
- Starting from an upcoming Opsview 6.11.x version, scheduled for release in the first week of April 2025, Opsview will support MariaDB 10.11 as the default database for RHEL 8.10 and RHEL 9.4 and above and OL 8 and 9, also as a non-default database for Ubuntu 20 and 22.
- Earlier versions of RHEL 8 and 9 will continue to support MariaDB 10.3 and 10.5, respectively, as default databases. However, we strongly recommend upgrading to the latest RHEL 8 and 9 versions for improved security.
-
End-of-Life (EOL) notice for operating system support
- Debian 12 support was introduced in the Opsview 6.10.3 release. This was done because Debian 10 is already at an End-of-Life (EOL) state.
- As a result, Opsview versions 6.11.0 and above will not be deployable on Debian 10. While we will continue to support existing Opsview versions according to our support policy, we strongly recommend migrating to an actively supported operating system. Given that Debian 10 will no longer receive security updates, it is crucial to prioritize system security.
-
End-of-Support (EOS) notice for Opsview 6.8.x versions
- With the release of Opsview 6.11.0, versions 6.8.x have reached their End-of-Support (EOS) status as per our support policy.
- This means that Opsview versions 6.8.x will no longer receive code fixes or security updates. The documentation for versions 6.8.9 and earlier will remain accessible for the time being, but it will no longer receive backported updates. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.
-
This release contains security fixes.
-
This release deploys the Opsview repository version
6.11.0.202502250725. -
This release deploys the Infrastructure Agent version 2.4.01315 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-71682 | The Status Objects tab has been updated to use an itemselector for adding and removing host groups, service groups, and hashtags when editing roles. This allows efficient selection of items displayed in a list format with search functionality for quick filtering of items. For more information, see Status Objects. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-55269 | Fixed an issue where AutoMonitor could not create host and host group names containing invalid characters. Invalid characters are now automatically removed before the names are imported into Opsview. The sanitized names are displayed in the scan logs. |
| OP-59714 | NGINX has been upgraded to resolve security issues with third-party software. For more details, see Web Server Software. |
| OP-69151 | The activemq-client library has been upgraded from 5.16.6 to 5.16.7 to address a security vulnerability. For more details, see Reporting Module. |
| OP-70400 | The Kubernetes and OAuthlib libraries have been upgraded to resolve multiple service checks failing for Azure Kubernetes Pods. For more details, see Python Libraries. |
| OP-71820 | Fixed an issue that caused remotely managed cluster upgrades to fail when the cluster names contained opsview cluster or opsview_cluster (case-insensitive). The failure was due to messagequeue user permission errors. Now, the upgrade process and the collectors’ messagequeues operate successfully. For more information, see Additional upgrade steps.
|
| OP-72068 | The ITRS Opsview Mobile App is back on Google Play after temporary unavailability. You can now install or update the app directly from the Play Store. |
| OP-72083 | Opspack: OS - VMware vSphere (v3.0.1) has been updated to support the monitoring of clusters and datastores with names containing spaces via vCenter v7 and v8. |
| OP-72188 | The pyopsview REST API client can now be used with multiple active connections to Opsview simultaneously. |
| OP-72369 | Fixed an issue where Debian and Ubuntu systems could not sync plugins due to errors in rsync packages that caused checks to fail after a reload. |
| OP-72963 | The check_wmi_plus plugin can now handle empty results when using the -4 option. |
| OP-73110 | Fixed an issue in the Reporting Module where deleted host entries incorrectly appeared in reports filtered by a hashtag. Now, hashtag filters are passed through via sub-reports. This ensures that they are correctly applied to the entire final report. |
Opsview 6.10.6 Copied
Released: 26 February 2025
Highlights Copied
These are the highlights of this release:
- This release deploys the Opsview repository version
6.10.6.202502251111. - This release deploys the Infrastructure Agent version 2.3.00494 for self-monitoring.
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-71820 | Fixed an issue that caused remotely managed cluster upgrades to fail when the cluster names contained opsview cluster or opsview_cluster (case-insensitive). The failure was due to messagequeue user permission errors. Now, the upgrade process and the collectors’ messagequeues operate successfully. For more information, see Additional upgrade steps.
|
Opsview 6.10.5 Copied
Released: 28 January 2025
Highlights Copied
These are the highlights of this release:
-
Secure Args
- Opsview can now pass arguments via standard input (stdin) to plugins, event handlers, and notification scripts by using Secure Arguments (also known as Secure Args). This enhances security as it prevents sensitive information like passwords and credentials from being displayed in the process list.
- To use this feature, you can create appropriate scripts and specify secure args compatibility during import. For more information, see Secure Arguments documentation.
-
When editing Hosts, the Variables tab now supports efficient deletion of multiple host variables at once.
-
System downtime no longer causes invalid stale results, which can remove non-sticky acknowledgments. Now, only valid stale states occur, preventing unwanted notifications.
-
The Navigator page and notifications now correctly reflect the selected objects for
VIEWSOMEusers with object permissions based on Hashtag Individual or Interface Tagging. -
The alert type
Ignoreis now available for SNMP interfaces. This lets you disregard the statuses of those interfaces that are expected to go down if you do not want to receive notifications about it. -
Opsview cronjobs can now handle a backup folder path that uses a symlink to another folder or drive.
-
End-of-Life (EOL) notice for operating system support
- Debian 12 support was introduced in the Opsview 6.10.3 release. This was done because Debian 10 is already at End-of-Life (EOL) state.
- As a result, newer Opsview versions (6.11.0 and above) released from end of February 2025 will not be deployable on Debian 10. While we will continue to support existing Opsview versions according to our support policy, we strongly recommend migrating to an actively supported operating system. Given that Debian 10 will no longer receive security updates, it is crucial to prioritize system security.
-
This release contains security fixes.
-
This release deploys the Opsview repository version
6.10.5.202501271040. -
This release deploys the Infrastructure Agent version 2.3.00494 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-64026 | When enabled, the Opsview - Updates survey now collects and reports your MySQL version and vendor information. This data enables Opsview to prioritize future database changes more effectively. |
| OP-66050 | For SNMP-enabled hosts, Ignore has been added as an available interface alert type. For more information, see Alert Type. |
| OP-69139 | Opsview now supports Secure Arguments (also known as Secure Args) to improve the security of plugins, notification scripts, and event handlers by passing arguments via standard input (stdin) instead of the command line. |
| OP-70586 | Multiple host variables can now be removed simultaneously via bulk selection. For more information, see Hosts. |
| OP-70669 | You can now set the execution style of uploaded plugins, notification scripts, and event handlers to use Secure Args for argument passing. This is the recommended approach for enhanced security. For more information, see Secure Arguments. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-69153 | Objects selected using Hashtag Individual Tagging and Interface Tagging for users with VIEWSOME now correctly display in the Navigator and send out notifications. For more details, see Adding a Hashtag. |
| OP-69614 | MessageQueue permissions have been updated to resolve issues with NetAudit backups on clustered systems. |
| OP-70401 | Fixed an issue where system downtime caused invalid stale results, which can wipe non-sticky acknowledgments on problem states. |
| OP-71571 | Opsview cronjobs can now handle systems where /opt/opsview/coreutils/var/backups uses a symlink to another drive. |
| OP-71733 | Fixed parsing issues in the check_wmi_plus plugin. Previously, range parsing in thresholds was incorrect. Additionally, the
|
| OP-71766 | The opsview-python3-modules package now correctly depends on libyaml for the appropriate OS. |
| OP-72188 | The pyopsview library provided in opsview-python3-modules has been upgraded to v6.2.5 to support multiple simultaneous connections. For more details, see pyopsview. |
Opsview 6.10.4 Copied
Released: 11 December 2024
Highlights Copied
These are the highlights of this release:
- VMWare vSphere Opspack enhancements
- VMWare vSphere Opspack now supports the monitoring of ESXi Hosts, Guests, Datastores, and Resource Pools running vSphere 8 as well as vCenter 8 environments. Environments upgraded to vCenter 8 or vSphere 8 will continue to be monitored correctly.
- It is able to monitor vCenter environments with nested datacenter folders correctly.
- Users and Roles improvements
- NetAudit now controls host visibility based on user permissions. Users will only see Hosts in the NetAudit feature that they have permissions to view.
- Users can now only set and cancel downtimes on Host Groups they can view, regardless of their
ADMINACCESSpermission. This resolves issues where users can set downtimes but are unable to cancel them. - There are now separate permissions for AutoMonitor and Autodiscovery. The
CONFIGUREHOSTSpermission no longer covers access for those two features. This enables more granular permission assignment.
- Agent Client improvements
- Additional positional arguments to the executor agent client (
check_nrpe) now correctly pass to agents, which allows you to continue using existing custom service checks that use additional positional arguments. This also fixes a behavior change from 6.9.2 when the originalcheck_nrpeplugin was replaced.
- Additional positional arguments to the executor agent client (
- Other improvements
- MySQL 8.0 is now supported as a non-default database choice for Opsview deployments on RHEL 9 and OL 9. See Supported Databases.
- Event Graph Dashlet can now be filtered by Host Groups properly.
- The option to use
ifNamefor the names of SNMP interfaces during an interface query is now enabled by default. This assists in detecting unique interface names. - The
check_snmp_memutilplugin can now gracefully handle scenarios where the total swap space is 0 or the OIDs for swap or real memory are nonexistent. You can now configure your devices to have no swap space or OIDs for swap or real memory as per your business needs while still monitoring memory utilization. - When the changelog is enabled, deleting an acknowledgment or cancelling a downtime will require a changelog message for proper audit tracking. This forces all your users to provide proper change messages when carrying out those actions.
- For Opsview Enterprise, threshold macros used in Dynamic Thresholds compatible with Service Checks have been changed from
WARNINGGTandCRITICALGTtoWARNINGDTandCRITICALDTrespectively. These macros support hard limits and default values. For more information, see Configuring Dynamic Thresholds.Required action
A reload is required to ensure continued use of Dynamic Thresholds with Opsview’s bundled service checks.
During the upgrade, prior to this reload, checks that support dynamic thresholds will fail. For this reason, it is important to disable checks during the upgrade as per Upgrade Opsview to avoid notifications being raised for these failing checks.
Furthermore, any custom checks using the Dynamic Thresholds macros must be updated to continue working.
It is recommended to check the page for Configuring Dynamic Thresholds before upgrading to see which custom checks need updating.
- End-of-Life (EOL) notice for operating system support
- Debian 12 support was introduced in the last release, Opsview 6.10.3. This was done because Debian 10 is already at End-of-Life (EOL) state.
- As a result, future Opsview versions (6.11.0 and above) released from end of February 2025 will not be deployable on Debian 10. While Opsview will continue to support existing versions according to the support policy, we strongly recommend migrating to an actively supported operating system. As Debian 10 will no longer receive security updates, it is crucial to prioritize system security.
- This release contains security fixes.
- This release deploys the Opsview repository version
6.10.4.202412091733. - This release deploys the Infrastructure Agent version 2.2.48243 for self-monitoring.
Known Issue
For the Opsview Mobile App login, you must use the https://legacy.opsview.com site to manage your account as there are errors currently affecting user registrations. For more details, see Opsview 6.x Known Issues.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-53802 | SNMP-enabled hosts now use the ifName field by default during interface querying. For more information, see Use SNMP ifName. |
| OP-54915 | The NetAudit UI has been updated to show hosts based on the permissions of the user. Ensure that you have the necessary permissions to view hosts. For more information, see NetAudit Troubleshooting. |
| OP-60756 | AutoMonitor and Autodiscovery apps now have their own access controls (AUTOMONITOR and AUTODISCOVERY), separate from the CONFIGUREHOSTS access for the Hosts List page. This provides more granular permission options. During the upgrade, any Roles with CONFIGUREHOSTS will automatically gain AUTOMONITOR and AUTODISCOVERY permissions to maintain behavior. Additionally, a security update has been implemented to prevent unauthorized changes. As a result, AutoMonitor now requires both CONFIGURESAVE and AUTOMONITOR permissions.
For systems using multi-tenancy, any primary or tenant roles with unauthorized access will lose those privileges during this upgrade. |
| OP-62629 | Opspack: OS - VMware vSphere (v2.1.0) has been updated. Opsview now supports vSphere 8 and vCenter 8.0 environments; the older versions of vSphere including 6.0, 6.7, and 7.0 continue to be supported, along with vCenter 6.7 and 7.0. |
| OP-67906 | For the Opsview UI, Angular has been upgraded from v12 to v17 to resolve security issues with third-party libraries. For more details, see NodeJS Modules. |
| OP-70306 | MySQL 8.0 is now supported as a non-default database choice for Opsview deployments on RHEL 9 and OL 9. See Supported Databases. |
| OP-70347 | Dynamic Thresholds for Opsview Enterprise have been updated to improve the calculation of threshold values and support hard limits. The threshold macros used in Dynamic Thresholds compatible with Service Checks have been changed from WARNINGGT and CRITICALGT to WARNINGDT and CRITICALDT. This macro rename means that custom checks using the old macros must be updated to continue working. |
| OP-70540 | Dynamic Thresholds algorithm for Opsview Enterprise has been improved to better support large metric value drops, which reduces noise generated by these changes. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-43192 | When the changelog is enabled, cancelling downtime or deleting an acknowledge will now require a changelog message. |
| OP-44293 | Fixed an issue in the check_snmp_memutil plugin where hosts without swap memory returned an Illegal division by zero error. Now, the plugin handles gracefully the instances where the total swap space is 0 or the swap and real memory have no existing OIDs. |
| OP-52700 | Opsview system SNMP configuration file permissions have been updated to allow read and write access only to the root user. |
| OP-61898 | AutoMonitor vSphere Express Scan and the OS - VMware vSphere Opspack now correctly handle nested folders in vCenter datacenters. |
| OP-65414 | When self-monitoring is being set up, disk partitions mounted to paths greater than 64 characters will not be included. |
| OP-69936 | Cloud - Azure Opspack documentation has been updated to include setting up the Azure Monitor Agent. This replaces the Log Analytics Agent for Azure VM Monitoring, which is a prerequisite for some Host Templates. |
| OP-70031 | Filtering by Host Group now works correctly for Event Graph and Event Table dashlets. Upon opening the configuration options of Event Graph and Event Table, an access denied box will no longer appear for users without the CONFIGUREVIEW permission. |
| OP-70150 | Fixed an issue with downtime creation where a user with ADMINACCESS can set downtime on objects they cannot view. Now, downtime creation and deletion both correctly affect objects a user is authorized to access. |
| OP-70284 | When there is a connection error in Nucleon RabbitMQ adapter used for opsview-messagequeue, the error logs now include the specific details of the connection error. |
| OP-70296 | Additional positional arguments to the executor agent client (check_nrpe) are now correctly passed to agents, which allows you to continue using existing custom service checks that use additional positional arguments. This also fixes a behavior change from 6.9.2 when the original check_nrpe plugin was replaced. |
| OP-71369 | Reporting Module has been updated to support additional OS Java versions to fix startup issues on RHEL 9 systems. |
| OP-71656 | Fixed an issue for Opsview Enterprise where service checks that use Dynamic Thresholds fail on collectors that run older versions than the Orchestrator. |
| OP-71702 | Fixed an issue where upgrading remotely managed collectors fail due to a missing message parameter if their starting version was too old. |
| OP-71717 | Fixed an issue where applying Notification Profiles in particular orders lead to invalid opsview-scheduler notification states. |
Opsview 6.10.3 Copied
Released: 30 October 2024
Highlights Copied
These are the highlights of this release:
- Debian 12 support
- Opsview and Infrastructure Agent can now be deployed on Debian 12 systems.
- Plugin enhancement
- The
check_apache_performanceservice check now handles properly the cases where there are workers gracefully restarted.
- The
- Configuration enhancements
- Hashtags can now be assigned to SNMP interfaces and their service checks.
- Added the ability to search for SNMP interfaces based on any text in their descriptions.
- Added text search for hosts on the BSM Components configuration screen.
- Apostrophes are now allowed in full names of users.
- Other improvements
- Scheduler now properly handles dollar signs (
$) in the service check commands – escaping them is no longer necessary. - Results Exporter now handles unsupported output types gracefully by reporting warnings through the logs.
- The API has been fixed to correctly enforce the limit on scheduled downtime to a maximum duration of one year, with an end date no later than one year from the current date. Note that this downtime previously did not work, but the API did not return an error.
- You can now correctly export Host Templates using plugins that are not in use by your hosts.
- Scheduler now properly handles dollar signs (
- This release deploys the Opsview repository version
6.10.3.202410221020. - This release deploys the Infrastructure Agent version 2.1.46997 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-53646 | Hashtags can now be assigned to SNMP interfaces on hosts and their service checks using the new Interface Tagging tab when creating or editing a hashtag. |
| OP-65602 | Improved selection of hosts by allowing text search in the BSM > Components configuration screen. |
| OP-66456 | When configuring new Business Services or Components, the Notify Via field now automatically pre-selects the first available cluster (the Master Monitoring Cluster). |
| OP-68053 | Results Exporter now handles unsupported output types by reporting warnings through the logs. |
| OP-69593 | You can now filter SNMP interfaces by extra text strings in the Interface name column when querying. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-42988 | Escaping of macro delimiter characters ( For backward compatibility, a pair of delimiter characters ( |
| OP-45379 | Audit logs no longer display notification script arguments after testing notifications. |
| OP-60757 | The full name field for users now supports apostrophes. |
| OP-65198 | The check_apache_performance plugin now handles properly the cases where there are workers gracefully restarted. |
| OP-65678 | Fixed an issue where the service tooltip on host in the Hashtag view displayed incorrectly. |
| OP-66065 | Opsview menu logo customizations now persist across upgrades. |
| OP-66163 | You can now correctly export Host Templates using plugins that are not in use by your hosts. |
| OP-67311 | The downtime REST API endpoint now returns a 400 error when a scheduled time with an end date or start time more than a year from the current date is created. Previously, this downtime would not work correctly, but the API would not report an error. |
| OP-67495 | Autodiscovery now truncates discovered hosts names to 64 characters to prevent import issues. |
Opsview 6.10.2 Copied
Released: 25 September 2024
Highlights Copied
These are the highlights of this release:
- Dynamic Thresholds enhancements
- Fixed failure to launch due to corrupt encrypted config files.
- The
opsview-sysinstall is now part of deploy role.
- SNMP enhancements
- Added support for interfaces with no speed.
- Added support for big integer (bigint) values for the throughput.
- The option
--ignore-strange-percent-valuesis now working as expected by ignoring results greater than 100.
- Other improvements
- Improved ODW import runtime especially for large systems.
- Added configurable cluster partition handling for RabbitMQ.
- Client certificates can now be generated with Email Subject Alternative Name (SAN) type.
- Notifications are now sent for services checks in a non-OK state after coming out of downtime.
- The
opsview-state-changescan now scale to multiple hosts by preventing message duplication and loss. - Improved deploy times by optimizing the number of times
ansible-interpreteris run. - Improved the
negatefunctionality in service checks by implementingnegatein the executor instead of using an external plugin.
- This release deploys the Opsview repository version
6.10.2.202409240749. - This release deploys the Infrastructure Agent version 2.0.45480 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-68362 | The opsview-sys-master package has been renamed to opsview-sys. It now creates configuration files as part of the deploy role, instead of during package build. |
| OP-68381 | Reduced the number of times the ansible-interpreter role needs to be run during deployment. |
| OP-68641 | You can now use the negate functionality implemented within the executor so that you get a more efficient system without the need to invoke an external plugin. |
| OP-68839 | Enhanced the deployment process by optimizing the use of ansible_managed to facilitate easier debugging of templated files. |
| OP-69261 | Improvements to SNMP Monitoring:
|
| OP-69976 | Improved performance of ODW importing. Please note that a new index has been added to the ODW database, which may result in a longer upgrade time. The new Daily Performance Summarized Report is three times faster and uses six times less disk space on the database server than the previous Daily Performance Report. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-53178 | The opsview-state-changes distribution system has been improved to prevent message duplication and loss. |
| OP-65941 | Fixed an issue that prevented notifications from being sent when a service returned from a downtime period. Notifications are now sent as scheduled after the downtime ends. |
| OP-67259 | Exceptions occurring in the opsview-common registry helper are now logged. |
| OP-67849 | Upon launching the opsview-dataserver service, the system now records the initial registration of endpoints in both the opsview.log and syslog files. |
| OP-68574 | Fixed an issue that prevented PKI from generating client certificates due to an incorrect FQDN on the collector. |
| OP-69263 | Under standard opsview-deploy configurations, when nodes experience intermittent network disconnections and reconnections (due to firewall actions, not VM suspensions), the system’s partition handling mechanism functions as expected. |
| OP-69273 | Fixed an an issue that prevented opsview-sys from starting due to corrupted encrypted configuration files. |
| OP-69740 | Fixed an issue that prevented the messagequeue node from joining the cluster when adding remote collectors. |
| OP-69779 | Fixed Opsview mobile push notification issues. |
Opsview 6.10.1 Copied
Released: 21 August 2024
Highlights Copied
These are the highlights of this release:
- Dynamic Thresholds
- Dynamic Thresholds dynamically adjust alert thresholds based on historical data, reducing noise and identifying anomalous behavior. This feature is available for Opsview Enterprise customers. For more information, see Dynamic Thresholds documentation.
- Forecasting
- Forecasting allows you to proactively, rather than reactively, monitor your infrastructure by utilizing visual forecasting. It helps detect issues early, before they escalate into incidents—such as storage drives running out of space, memory leaks, or CPU utilization growth. This capability is accessible through the Obcerv UI and can be used effectively with as little as one day of data. This feature is available for Opsview Enterprise customers. For more information, see Forecasting documentation.
- Ubuntu 22 support
- Opsview and Infrastructure Agent can now be deployed on Ubuntu 22 systems.
- Other improvements
- Infrastructure Agent no longer runs as the root user on your monitored hosts.
- NetAudit now allows bulk password resets for multiple hosts.
- Additional feature enhancements and security fixes.
- This release deploys the Opsview repository version
6.10.1.202408161522. - This release deploys the Infrastructure Agent version 2.0.45314 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-65613 | NetAudit now allows bulk password resets for multiple hosts. |
| OP-67475 | Opsview and Infrastructure Agent can now be deployed on Ubuntu 22 systems. Please note a known issue affecting Ubuntu 22 repositories when using apt. |
| OP-67434 | Dynamic Thresholds configuration is now available, providing visualization of current threshold values added or those awaiting data. Additionally, the opsview-sys-master component is installed and configured on the Orchestrator host as part of the setup-everything.yml playbook, managed by Opsview Deploy. Alternatively, the sys-master-install.yml playbook can be used for standalone installation and configuration. |
| OP-67436 | Updated Opspack: Export - Capacity Planner (v1.2.0). Increased the NRPE timeout for the Cap Plan Export - Server - Utilization Service Check to 20 seconds. |
| OP-60925 | Unmanaged databases can be integrated with Opsview using a non-root user. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-65816 | The certificate validation process now successfully handles certificates generated by easyrsa (using server-cert PKI command) that contain a mix of FQDNs, IP addresses, and email addresses in their Subject Alternate Names (SANs) list. |
| OP-67080 | Remotely managed collectors can be deployed with or without SSH tunnels, regardless of whether the deployment uses separate registry or messagequeue servers. |
| OP-68638 | Fixed an issue with the SNMP Traps feature where traces could not be started correctly due to messagequeue permissions. |
| OP-67684 | Fixed the following issues in the check_nrpe plugin:
|
| OP-68659 | Fixed broken link to Default thresholds on the Interfaces tab within Host configuration. |
| OP-68984 | Fixed an issue where the scheduler would restart due to missing agent_config keys in messages. |
| OP-64009 | Errors during scheduled NetAudit collection are now logged to syslog rather than being lost. |
Opsview 6.10.0 Copied
Released: 17 July 2024
Highlights Copied
These are the highlights of this release:
- Google Cloud Platform (GCP) monitoring improvements
- Reduced CPU utilization for the
check_gcpplugin when running multiple concurrent checks. - Enhanced security for argument passing within the
check_gcpplugin.
- Reduced CPU utilization for the
- Other improvements
- Introduced the ability to select an Alert Type for SNMP Interfaces, and a new Dormant alert type.
- Improved error logging in dataserver component to capture details of any MessageQueue connection failures.
- Addressed security vulnerability by upgrading Apache Tomcat used in the Reporting Module.
- End-of-Life (EOL) notice for operating system support
- As previously announced, Opsview is ending the support for CentOS 7, OEL 7, RHEL 7, and Ubuntu 18, as these operating systems have reached their End-of-Life (EOL) status. This means that this Opsview version will not be available to deploy on these operating system versions. We will continue to support existing versions of Opsview per our Support policy, but we recommend that you migrate to an actively supported OS version given that vendors will no longer be providing security updates.
- Supported database notice
- As previously announced, Opsview now only supports the default database client or server provided with each supported operating system per our Supported databases policy.
- End-of-Life (EOL) notice for support of TLS v1.1 and ADH Ciphers
- TLS v1.1 was deprecated in March 2021 (RFC 8996) and we strongly recommend against its use. Additionally, use of ADH (Anonymous Diffie-Hellman) ciphers is strongly discouraged due to vulnerability to man-in-the-middle attacks as outlined in (RFC 4346). As a result, they will no longer be supported in a future version of Opsview 6.10.x. We will continue to support existing versions of Opsview per our Support policy, but we recommend that you reconfigure to use a newer TLS version and stronger cipher suites if affected.
- This release deploys the Opsview repository version
6.10.0.202407151740. - This release deploys the Infrastructure Agent version 1.3.44641 for self-monitoring.
New features and enhancements Copied
These are the highlights of this release:
| Issue key | Description |
|---|---|
| OP-45872 | Since Opsview no longer provides any plugins requiring PowerShell on collectors, PowerShell is excluded from fresh Opsview installations. However, existing Opsview-provided PowerShell will continue to be upgraded and now uses version 7.4.2. |
| OP-63619 | Introduced the ability to select an Alert Type for SNMP interfaces. Existing SNMP interfaces will continue to use the Normal alert type, which maintains their current behaviour. The new Dormant alert type is now available for interfaces that are expected to be down, and detects if their admin status changes to up unexpectedly. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-56850 | When a host check recovers from dependency failure, while its dependent checks remain in a dependency failure state, the output now displays Dependency failure: Host X is recovering. |
| OP-60213 | Apache Tomcat used by the Reporting Module has been upgraded to 9.0.89 to address security vulnerabilities. |
| OP-63085 | Updated Opspack: Cloud - GCP (v1.0.6). Reduced CPU utilization for the check_gcp plugin when running multiple concurrent checks, and made argument passing more secure. |
| OP-64217 | The dataserver component now logs error messages to capture details of any MessageQueue connection failures. |
| OP-66858 | The restart snmpd playbook task now runs successfully when deploying or upgrading Opsview, irrespective of default OS snmptrapd user. |
| OP-67404 | Fixed several minor UI issues on the Collector Management page:
|
Disclaimer
The information contained in this document is for general information and guidance on our products, services, and other matters. It is only for information purposes and is not intended as advice which should be relied upon. We try to ensure that the content of this document is accurate and up-to-date, but this cannot be guaranteed. Changes may be made to our products, services, and other matters which are not noted or recorded herein. All liability for loss and damage arising from reliance on this document is excluded (except where death or personal injury arises from our negligence or loss or damage arises from any fraud on our part).