Opsview 6.x Release Notes
Overview
Opsview release notes contain the list of enhancements of features, and a set of issues fixed in the 6.x
release version of Opsview Monitor. Note that any fixes from previous release dates are rolled up into the latest release.
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.
For Opsview 6.7.x and older release notes, you can still access them at the Opsview Knowledge Center.
Opsview 6.8.0
Released: 25 January 2023
Issue key | Description |
---|---|
OP-34170 | The database tables now use the same character set consistently. |
OP-51975 | VMware and HyperV virtual appliances no longer ship with the default SNMP community string configured. |
OP-52382 | All Opsview MySQL databases, such as opsview, runtime, ODW, and dashboards can now accept complete UTF-8 characters. |
OP-55866 | Initial UTF-8 support includes using scandic characters. |
OP-55888 | Starting with the Opsview 6.8.0 release, you can find the documentation, including the ITRS Opsview Cloud Documentation, at ITRS Opsview Documentation. |
OP-56537 | All Golang components are now compiled using the updated toolchain. Both the go.mod and go.sum files no longer ship with the product. |
OP-56835 | The Notification method variable no longer fails when it accepts more than 128 characters. |
OP-56943 | Removed duplicate validation messages in the NetFlow source IP field. |
OP-56987 | Fixed a UI issue with the Host Group modal. |
OP-57069 | Upgrading from Opsview 6.8.0 where UTF-8 data is present now works correctly. |
Opsview 6.7.6
Released: 2 November 2022
Issues fixed
These are the issues we have fixed in this release:
Issue key | Description |
---|---|
OP-24136 | You can now configure the monitoring pages with a particular refresh interval and save the changes. |
OP-43034 | Fixed an issue where NetAudit failed to process messages due to an error found in the configuration file. |
OP-44544 | You can now use AWS roles in the check_aws_cloudwatch plugin. |
OP-45903 | The validation field warning messages now display the correct messages when the name value of a variable exceeds 63 characters. |
OP-46746 | Upgraded Jasper to version 8.1.0 and Tomcat to version 9.0.65. |
OP-47063 | For a specific user, you can now remove host group access to ensure that modifications are applied appropriately after a reload. |
OP-47728 | The opsview-data-access is now available for use in the opsview-notification-center component. |
OP-48227 | You can now search and filter host templates that are available using the Host Templates search field. |
OP-50991 | You can now view the Network Topology map correctly when the VIEWALL permission has been set. |
OP-51966 | Corrected tooltip description on the Monitoring Collectors page. |
OP-53513 | Using vCenter credentials, the ESXi servers (host and guest) can now be monitored without requiring additional credentials. |
OP-53812 | A new NTVIEWALL permission has been created to prevent viewing any hosts that are not imported within the Network Topology map. |
OP-54084 | An error when querying recent versions of Elasticsearch has been resolved. |
OP-54241 | Improved NetFlow Dashlet to provide better visualisation of NetFlow traffic. |
OP-54615 | A new support for field operations, replace[<str>][<str>] , has been added to the Obcerv mappings. Note that chaining operations is not supported, so you cannot configure `%( |
OP-54616 | Added Capacity Planner integration Opspack using OLD Windows and Linux agents. |
OP-54617 | A new output type for Obcerv outputs available in the results exporter can now send data into Capacity Planner. |
OP-54917 | The Entity Attributes exported by the Obcerv integration have been set to inheritable=false . |
OP-55020 | Fixed the NetFlow security vulnerability issue that prevented the API command injection (CVSS v2 8.5). |
OP-55106 | Fixed an issue where the progress bar for applying changes closes quickly before the assertion check is done. |
OP-55108 | The host icon management now works correctly. |
OP-55118 | Corrected a typographical error in the Status Access > Network Topology. |
OP-55412 | Improved performance response of the opsview_flow command. |
OP-55413 | A TTL (time to live) has been added to any flow requests made through 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 temporarily stopped. |
OP-55450 | The opsview-flow-collector component has been made more resilient to any messagequeue failures, so it now reconnects automatically. |
OP-55548 | Specific collectors have been set for flow-collector to load balance the sources manually. |
Opsview 6.7.5
Released: 6 September 2022
Issues fixed
These are the issues we have fixed in this release:
Issue key | Description |
---|---|
OP-48906 | ProCheckUp: Privileged administrative functions no longer require password. When setting up Opsview Cloud system, the NOPASSWD flag has been removed from the users sudo configuration. This ensures users performing administrative functionality are asked to explicitly re-enter a strong password. |
OP-51564 | Notifications are now triggered not only when an object changes state but also when some configuration changes are applied that would have triggered a notification when the current state happened. This enables Opsview to notify new teams or individuals about existing problems in the system. |
OP-52201 | ProCheckUp - Opsview Software Version Disclosure (CVSS: 1.8). ProCheckUp performed a round of web app pen testing. |
OP-53112 | Notifications are now working until service check goes back to an OK state. |
OP-53127 | Uptrends integration allows real and synthetic monitoring data to be displayed in Opsview Monitor. |
OP-53136 | You can now run the Agent as a daemon on both Linux and Windows hosts so that it can always be running in the background and available to run checks, even after machine reboot. |
OP-53137 | You can now install the Agent through the following: a single package file, from apt, or yum repository. This makes the installation for the Agent easier. |
OP-53138 | You can now install the Windows Agent to monitor your Windows system with a lightweight process. |
OP-53142 | You can now run and validate all the existing NSClient++ checks against the new agent to prevent losing any checks when switching to the new agent. |
OP-53229 | Opsview Monitor and Opsview Cloud PRE release activities and preparation for automation runs. |
OP-53653 | When deploying Opsview, the deployment process completes correctly and no warnings are shown when running setup-everything/opsview . |
OP-53844 | Implemented service check poller. Built-in checks are now available which return aggregated metrics from data gathered (polled) on a regular schedule. This ensures the aggregated metrics to return more accurate data. |
OP-53939 | Fixed an issue that generates an error Method not allowed in the Notification Profiles when clicking Objects Selected. |
OP-53956 | Fixed an issue in SSO/OAuth2 login that led to the Content Security Policy (CSP) error. |
OP-53997 | Fixed an issue that caused the Access Denied page to refresh every second. |
OP-54117 | Improved the collection of Uptrends data to be displayed in the Opsview Monitor.
|
OP-54140 | Fixed an issue that prevented state updates by causing passives to become trapped in the results forwarder cache queue. |
OP-54261 | Fixed an issue in the sync monitoring script that caused the plugin permission to be broken. |
OP-54496 | Idle session timer now works correctly before logging out. |
OP-54562 | Jasper server deployment now installs correctly when using Opsview managed database and external database using TLS. |
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).