×
![]()
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.8
Released: 1 November 2023
Highlights
These are the highlights of this release:
- The Opsview mobile app has been improved with the following updates:
- You no longer need to re-authenticate frequently to receive alert notifications.
- Security has been enhanced with an encrypted storage library.
- Infrequent authentication failures have been resolved.
- Remotely managed collectors have been improved in the following ways:
- The user experience for registering new remote collectors has been improved, with better status updates for both successful and failed registrations.
- Error logging has been enhanced to help users and administrators quickly identify and resolve issues.
- Security for session tokens during setup has been enhanced.
- Opsview can now distinguish between built-in Opsview plugins and files, and user-uploaded plugins and files. As a result of this change, there are several important changes to Opspack and plugin installation procedures:
- The post-upgrade steps for updating Opspacks have been changed to add a new required
-Bflag. See Upgrade Opspacks. - Plugins can now only be imported via the UI or REST API, instead of copying them directly to the filesystem. See Importing a Plugin.
- Plugin or plugin-related Opspack files cannot be imported if their name clashes with an existing Opsview-provided plugin or file. If this happens, you should rename the file you are trying to upload.
- The post-upgrade steps for updating Opspacks have been changed to add a new required
- A new script called
orchestratorimportscriptshas been added toopsview-orchestrator. This script helps Opsview Monitor administrators install event handlers, notification scripts, and other non-plugin files in the/opt/opsview/monitoringscriptsdirectory, ensuring that all files are placed in the correct location with the correct permissions and ownership. Please note that this tool cannot be used to import plugins. They must be imported either through the UI or the REST API. - This release deploys the Opsview repository version
6.8.8.202310241503. - This release deploys the Infrastructure Agent version 1.1.36971 for self-monitoring.
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Description |
|---|---|
| OP-61526 | You can now view the Collector Management upgrade log files in the user interface, which makes it easier to debug upgrade issues. |
| OP-61567 | The following Opspacks have been updated:
|
| OP-61665 | The address of the remote system is now included in the audit log record when a collector registration or cluster upgrade is started. This allows you to track where the remote registration request was made. |
| OP-61666 | Remotely managed collectors can now automatically monitor their own disks, so you can track their status without having to manually add the disks to your monitoring configuration. |
| OP-61783 | A new script called orchestratorimportscripts has been added to opsview-orchestrator. This script helps Opsview Monitor administrators install event handlers, notification scripts, and other files in the /opt/opsview/monitoringscripts directory, ensuring that all files are placed in the correct location with the correct permissions and ownership. During the upgrade, any directories that have previously been created under /opt/opsview/monitoringscripts/etc, /opt/opsview/monitoringscripts/plugins, /opt/opsview/monitoringscripts/notifications, and /opt/opsview/monitoringscripts/eventhandlers will be updated to have the owner root, the group opsview, and the permissions 770. |
| OP-61784 | The post-upgrade steps for updating Opspacks have been updated, see Upgrade Opspacks. Opsview has changed how to import plugins and Opspacks:
|
| OP-62420 | Collector Management now allows you to access the log API while an action is in progress, such as during a registration or update. This means that you do not have to wait for the action to complete or time out before you can view the logs. |
| OP-62680 | Collector Management has added the following options to help identify and troubleshoot registration and upgrade issues:
|
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-38891 | Fixed an issue where service dependencies were not correctly handled when multiple service checks were created. Previously, child service checks would continue to run even after the parent service check had failed. This could cause incorrect notifications to be sent out. |
| OP-56894 | Fixed an issue where the setup-monitoring playbook failed when change logging was enabled. This means that you can now register and update remotely managed collectors when the change logs are enabled. |
| OP-62062 | Fixed an issue where the font becomes invisible when the mobile app is in dark theme. |
| OP-62080 | Fixed several issues in the Collector Management user interface, including:
|
| OP-62633 | Audit events for remote collector registration request and completion have been moved from the CONFIG to the ACTION category. |
| OP-62656 | The Hyper-V VA image can now be used on a disk that is larger than 20 GB, which allows for more data to be stored and used. This unblocks Hyper-V VA deployments. Note that the VA contains Opsview version 6.8.7. |
| OP-62838 | Session tokens are now more secure and are no longer displayed on the command line to improve security. This means that the session token is not passed to opsview-deploy or curl, or it is not saved in the Ansible log, logged command line, or verbose logging (-vvv). |
| OP-62933 | The remote collector upgrade utility now logs events to help users diagnose problems. Additionally, startup problems with the upgrade utility are now reported to the data server. |
| OP-63073 | Collector registration now works on all supported operating systems. Previously, using an old version of curl would prevent you from registering collectors. |
| OP-63102 | Fixed an issue where the WebSocket sent multiple messages to the front end when status changes occurred in a Collector Management cluster. This could cause messages to be displayed to the user more than once. |
Opsview 6.8.7
Released: 28 September 2023
Highlights
These are the highlights of this release:
- Collector and cluster upgrade notifications are now available through toast messages. These messages will keep you informed of the status of your upgrade, including when it starts, succeeds, fails, or when a cluster or collector is deleted.
- Collectors can now be automatically self-monitored by the cluster when they use SSH tunnels to connect to the master.
- The address of the remote system is now included in the audit log record when a collector registration or cluster upgrade is started. This allows you to track where the remote registration request was made.
- This release deploys the Infrastructure Agent version 1.1.36127 for self-monitoring.
For more information, see What’s New in Opsview.
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Description |
|---|---|
| OP-58270 | Collectors can now be automatically self-monitored by the cluster when they use SSH tunnels to connect to the master. This means that you no longer have to manually reconfigure collectors when you want to use SSH tunnels to connect to the master. |
| OP-59667 | The dataserver progress API has been updated to handle reports with an attached log file for remotely managed collector registrations and upgrades. This lets Opsview administrators diagnose problems with remotely managed collector registrations and upgrades by viewing the attached log file. |
| OP-59908 | The following Opspacks have been updated: Application - Opsview (v3.1.0), Opsview - Self Monitoring (v3.0.0). Also, the Opsview - Login Service Check now supports systems with and without TLS enabled. |
| OP-59909 | You can now see toast messages when triggering an upgrade. This will notify you of collector upgrade events so that you can be aware of the status of your upgrades and take any necessary action. |
| OP-61657 | The dataserver now provides reload events to all applications. This allows applications to react to changes in the dataserver, if necessary. Previously, the orchestrator sent reload events to the dataserver, but these were ingested by Network Topology. Now, the events are ingested by the dataserver and then passed to any services that have subscribed to reload events. |
| OP-61665 | The address of the remote system is now included in the audit log record when a collector registration or cluster upgrade is started. This allows you to track where the remote registration request was made. |
| OP-62094 | The Apply Changes modal now shows how many configuration changes have been updated from the command line (by the SYSTEM user). The opsview_sync_ldap now also logs progress messages to the Audit Logs using the ACTION category (instead of the CONFIG category). |
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-59115 | The Orchestrator and Scheduler now shut down correctly. This prevents old Orchestrator and Scheduler processes from running and causing the Opsview service to be in a bad state after an upgrade. |
| OP-61939 | Remote collectors can now be installed using the same repository as the master. This simplifies the installation process and makes it easier to keep remote collectors up-to-date. |
| OP-62341 | Administrators are now notified of failures to upgrade remotely managed clusters, which allows them to investigate the failures and take appropriate action. |
Opsview 6.8.6
Released: 31 August 2023
Highlights
These are the highlights of this release:
- A new concept of Remotely Managed Collectors has been introduced.
- Remote Collectors can be upgraded to later versions directly from the user interface, without the need for command-line access (CLI).
- You can conveniently view the upgrade progress in the UI, with upgrade activities also logged and displayed.
- Collectors can now be installed and registered using a single command, which makes the process much easier. This command downloads and installs the Opsview software and registers the collector with the Orchestrator.
- For more information, see the Remote Collector Management documentation.
Known issue
There is a known issue that can cause Remote Collectors to fail to register with the error message
Failed to install Opsview Deploy. To fix this, make sure that you have the latest relevant 6.8.6 packages and configuration on your orchestrator system as follows:- On Ubuntu and Debian systems:
curl -sLo- https://deploy.opsview.com/6.8.6 | sudo bash -s -- -A repo && sudo apt update && sudo apt install -y opsview-deploy && sudo /opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/orchestrator-install.yml - On Centos, OL, and RHEL systems:
curl -sLo- https://deploy.opsview.com/6.8.6 | sudo bash -s -- -A repo && sudo yum makecache && sudo yum install -y opsview-deploy && sudo /opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/orchestrator-install.yml
The updated packages should have the specific versions:
opsview-dataserver:6.8.6.202309041305opsview-deploy:6.8.6.202309041306
- On Ubuntu and Debian systems:
- The Monitoring Collectors page has been replaced by the Collector Management page, which has been updated to ensure that all elements are aligned and styled consistently throughout the user interface.
- You can now install, configure, and update
opsview-results-exporterwithopsview-deploy.- This can save time for deployment or upgrades, mitigate the risk of human error, reduce confusion due to inconsistent deployment methods, and ensure that you are always using the latest, secure component configuration throughout your environment.
- For more information, see the Exporting Results and Results Exporter documentation.
Required action
We recommend migrating any existing Results Exporter installs to Deploy Managed mode. Please read Migration from manually installed Results Exporter.
Moreover, the execution of the
check_deployplaybook will raise warnings on systems with a previously manually installed Results Exporter until the migration is complete.
- This release deploys the Infrastructure Agent version 1.1.35674 for self-monitoring.
For more information, see What’s New in Opsview.
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Description |
|---|---|
| OP-31981 | Opsview administrators can now install, configure, and update opsview-results-exporter with opsview-deploy. This will save time for deployment or upgrades, mitigate the risk of human error, reduce confusion due to inconsistent deployment methods, and ensure that you are always using the latest, secure component configuration. |
| OP-58460 | The readability of command-line arguments in the user interface has been improved by using a monospaced font, which makes the text easier to read. |
| OP-58478 | Opsview administrators can now use the web UI to manage collector upgrades remotely. This means that you no longer need to access the collector command line to upgrade collectors. |
| OP-58520 | Websocket connections from the dataserver are now permitted for secure authorized access to display collector update progress. |
| OP-60324 | This includes the following changes:
|
| OP-61021 | The current Opsview version on the orchestrator host is now accessible through the database. |
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-38325 | You can now delete users and bulk hosts without any errors when the changelog is enabled. |
| OP-43652 | State history retention and audit log retention are decoupled. The new State History Retention setting in My System covers downtimes, acknowledgments, and object event history. This also fixed UI issues during post-Apply Changes backups. For more information, see the My System > Options documentation. |
| OP-56199 | This change ensures that setup-monitoring can be run successfully on all systems with more than 9 collectors without encountering a deadlock error. This error occurs when setup-monitoring tries to register too many collectors at once. |
| OP-57192 | Updated product documentation links to ensure that they direct users to the correct sections in the ITRS Opsview documentation. |
| OP-60167 | The opsview-netaudit-collector package now includes the additional patched files listed in the Makefile to ensure that the package works correctly. |
| OP-60292 | The Collector Management page has been updated to ensure that all elements are aligned and styled consistently throughout the user interface. |
| OP-60554 | The responses from the dataserver have been refactored to return JSON instead of HTML. This makes error handling easier when calling the dataserver API. |
| OP-61307 | The deploy variable that was previously known as opsview_results_exporter_custom_outputs is now called opsview_results_exporter_outputs. For more information, see the Exporting Results and Results Exporter documentations. |
| OP-61402 | Remotely managed collectors can now be installed and upgraded on both standard systems and rehomed systems. |
Opsview 6.8.5
Released: 20 July 2023
Highlights
These are the highlights of this release:
- The Reports module (JasperServer) has been updated to the latest version 8.2.0 on all of our supported operating systems.
- Opsview Monitor now supports running on Oracle Linux 8.
- The ITRS Infrastructure Agent is no longer in beta and can now be used as a stable alternative to the Opsview and NSClient agents for most Service Checks. It is a new way to monitor your IT infrastructure and can be installed on servers running on either Windows or Linux systems. We recommend that new and existing users use the ITRS Infrastructure Agent for new monitoring deployments, even though the Opsview Agent is still supported and available.
- The Opsview documentation version 6.8.4 or earlier remains a resource for Opsview Agent information, but we recommend that you use the ITRS Infrastructure Agent documentation.
- For migration steps on monitored hosts, see the Migrate from Opsview Agent documentation.
- This release deploys the Infrastructure Agent version 1.0.34422 for self-monitoring.
For more information, see What’s New in Opsview.
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Description |
|---|---|
| OP-49589 | Perl modules have been updated to fix security vulnerabilities. The following Opspacks have been updated to use the new modules:
|
| OP-51093 | The Sentinel RMS has been updated to ensure that Opsview licensing continues to function. |
| OP-54854 | The NOTICE logs now include more detailed information about SSH tunnels that fail to set up ports. |
| OP-57999 | MySQL no longer requires RELOAD permission on new or upgraded systems. |
| OP-58475 | The scheduler now handles requests for collector updates. Additionally, it invokes the update utility and sends the appropriate response message. |
| OP-58764 | The dataserver now has an API that allows users to update collectors (only for the update cluster). Additionally, the dataserver sends a request message to the scheduler and handles the response from the scheduler. |
| OP-60234 | The command line options for registering collectors have been improved. The help text now includes both long and short command line options, and the options are consistent with those used for collector upgrades. Additionally, a new option, -k --insecure, has been added to disable certificate checks when using the dataserver APIs. |
| OP-60242 | The validation of create and delete requests in the Collectors interface has been improved. |
| OP-60327 | Opsview Monitor can now be deployed on OEL 8 systems. |
| OP-60455 | The ITRS Infrastructure Agent is no longer in beta and can now be used as a stable alternative to the Opsview and NSClient agents. Please refer to the ITRS Infrastructure Agent documentation. |
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-47629 | The Last Check column in Checker has been expanded to fill the width of the column, allowing all of the information to be displayed. |
| OP-56075 | Apache Tomcat and Reports module (JasperServer) have been updated to the latest versions to fix security vulnerabilities. |
| OP-56868 | Updated Opspack: Application - Microsoft 365 (v2.0.8). Fixed an issue where the check_microsoft365 plugin was unable to correctly parse API data for the following Service Checks:
|
| OP-57192 | Updated product documentation links to ensure that they direct users to the correct sections in the ITRS Opsview documentation. |
| OP-60671 | For systems with remote databases that are managed by deploy, the orchestrator host will now have the same database vendor and version as the remote host, as long as both hosts are running the same operating system. If you encounter any problems upgrading your databases, please read this support article. |
| OP-60841 | Autodiscovery can now detect Infrastructure Agents running on scanned hosts in most cases. For more information, see Autodiscovery Detection Mapping. |
Opsview 6.8.4
Released: 14 June 2023
Highlights
These are the highlights of this release:
- Results Exporter improvements.
- The Results Exporter now allows advanced users to configure custom retrieval rules and transformations across their hosts and services. This data from Opsview can then be exported to a variety of destinations, including logging servers, files on disk, or external services like Splunk. Efficient data access and fine-grained component controls provide customization options to suit any estate size.
- Results Exporter users can now also use powerful filtering tools, allowing them to hold, remove, or process results as required to suit any situation.
Required action
After upgrading Opsview, if you are using Results Exporter, make sure that thecommand_queueandruntime_databasesections fromresultsexporter.defaults.yamlare copied into yourresultsexporter.yamlfile. Then, you need to override the credentials in these sections with the correct credentials. For more information, see Results Exporter administration.
- The Infrastructure Agent (Beta) and plugin repositories are now in general availability, which you can access from ITRS GitHub.
For more information, see What’s New in Opsview.
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Description |
|---|---|
| OP-52775 | The Results Exporter component now supports additional field mapping options, including string replacement and querying data from the Opsview system to enhance exported messages. As a result, the component requires additional credential configuration to function properly. After upgrading Opsview, ensure that the command_queue and runtime_database sections from resultsexporter.defaults.yaml are copied into your resultsexporter.yaml file. Then, you need to override the credentials in these sections with the correct credentials. For more information, see Results Exporter administration. Two new self-monitoring checks will be applied to hosts running a Results Exporter as part of the upgrade. After upgrading Opspacks and the setup-monitoring.yml playbook, run:
|
| OP-56011 | The Infrastructure Agent and plugin repositories are now in general availability, which you can access from ITRS GitHub. |
| OP-56754 | Infrastructure Agent now accepts requests from check_nrpe with arguments after -a having the arguments in the right order: check_nrpe -H host -C command -a "arg1" "arg2". |
| OP-58473 | The check-deploy playbook is now run as part of collector updates. |
| OP-58481 | Opsview administrators can now clean up any remotely managed collector upgrades that have stopped responding. Stalled updates are also logged and terminated. |
| OP-58585 | The opsview-deploy package will now upgrade to the latest version before attempting to run any playbook during a remote collector update. |
| OP-58597 | The collector upgrade utility now provides updates on its progress using the Dataserver API. The Ansible log is also included, where applicable. |
| OP-58599 | The web user interface for accessing the datastore has been updated to include views that allow users to easily access data for each cluster or collector. |
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-52757 | Results Exporter now deletes unused message queues at start-up. If any outputs are removed from the component configuration file or commented out, any messages still in the queues will be deleted, and no new messages will be collected for those outputs. To replicate the previous behavior of putting the output into a state where messages are collected but not exported, you can now use the new built-in hold filter. |
| OP-58373 | Only one collector can be registered in a cluster at a time. Previously, registering a second collector before the first one had finished caused errors and deadlocks. |
| OP-59389 | Infrastructure Agent no longer stops working when the hostname does not match the certificate. |
| OP-59428 | When a collector in a cluster is monitoring another collector in the same cluster, checks run via the monitored collector now return working results. |
| OP-59706 | When the default Linux agent is built from the source, it starts up without any errors and creates and uses self-signed certificates in its var directory. |
| OP-59719 | Updates have been made, allowing the opsview-dataserver to:
|
Opsview 6.8.3
Released: 25 May 2023
Highlights
These are the highlights of this release:
- The default NRPE ciphers have been amended to work with both the old Opsview Agent and new Infrastructure Agent. This change simplifies the migration from the Opsview Agent to the Infrastructure Agent, making it a viable alternative for monitoring deployments. For more information, see Default TLS Ciphers.
- A new permission called
RELOADVIEWhas been added. This new permission allows Opsview User Roles to view the Apply Changes status without being able to Apply Changes themselves. TheRELOADACCESSpermission still controls which Roles are able to apply changes.- Users who are granted the
RELOADVIEWpermission can only doGETrequests for/rest/reloadand can only view (read-only) the current state of the system. - Users who are additionally granted the
RELOADACCESSpermission can doGETorPOSTrequests for/rest/reloadand can view and make changes (read and write) to the system. - Any roles with the existing
RELOADACCESSpermission will automatically be granted theRELOADVIEWpermission during the upgrade process. - For more information, see Reload - Request Format.
- Users who are granted the
- The permissions for the Monitoring Collectors page have been updated to prevent unauthorized users from viewing clusters and collectors.
For more information, see What’s New in Opsview.
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Description |
|---|---|
| OP-45558 | Opsview Deploy logs now include the version number of Deploy at the top of all log files for easier debugging of deploy issues. |
| OP-52758 | Added a new RELOADVIEW permission to control read-only views in the Apply Changes status. |
| OP-53118 | You can now deploy multi-collector clusters in a new installation without having shell access to Orchestrator or a cloud platform. This improves the resilience and scalability of the collector clusters. |
| OP-57238 | The help text is available in every service check included with Windows builds of the Infrastructure Agent when called using the appropriate arguments. |
| OP-57644 | Added local and remote port forwarding to the tunnels, enabling users to use more services without having to open more firewall ports. |
| OP-58370 | New licensing information has been added to the infrastructure-agent plugin repositories for both Linux and Windows. |
| OP-58471 | Collector management now has a new database called opsview-managed-clusters. Similar to the opsview-system-status database, this new database uses the same key format. The timestamps are UTC in ISO format: yyyy-mm-ddThh:mm:ss.ssssss, for instance, 2023-04-12T11:51:03.698321. |
| OP-58476 | The dataserver now supports an API for collector updates. |
| OP-58583 | The update utility now prompts the user for their credentials before authenticating via the REST API. This ensures that the user’s password is not exposed on the terminal. The update utility then uses the acquired session ID to perform the update process. |
| OP-58584 | The admin of a remotely managed collector can now update the utility to ensure the version is updated in user_vars.yml. |
| OP-58755 | Added a new feature that allows the administrators to invoke a collector update API from the collector. |
| OP-59498 | If more than one LDAP realm is set up and one of them lacks the necessary configuration files and folders, the other realms are continuously processed. |
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-55094 | Fixed an issue where users with restricted access to the monitoring servers could access all of the monitoring servers. |
| OP-57837 | When a restore fails, the audit log now shows the error message. The error details are now recorded in the restore log, and the lock is released to make another attempt. |
| OP-58356 | Fixed the Navigator check box visual issue after Apply Changes has completed. |
| OP-58405 | Fixed an issue where Agent Python plugins failed when outputting UTF-8 on some operating systems. |
| OP-58621 | When a backup is restored, the backup IDs continue incrementing correctly without gaps or overlaps. |
| OP-58681 | Default NRPE ciphers have been amended to work with old and new Infrastructure Agent. |
| OP-58831 | Corrected the location path of the extracted plugins, which can be found in <agent-root>/plugins/, when extracting the source build. |
Opsview 6.8.2
Released: 19 April 2023
Highlights
These are the highlights of this release:
- New Infrastructure Agent.
- A new self-monitoring host template was added as part of Opsview deploy.
- Support for easier certificate management using self-signed certificates.
- Help documentation has been added to all Linux plugins.
- Secure cipher out of the box.
- It is no longer a requirement for a user to manually add certificates for secure communications.
- LDAP sync script updated.
- Improved
opsview_sync_ldapscript that is used for syncing Opsview users and roles with an LDAP or Active Directory server. - Group files must now have an
.xmlextension to be processed correctly. - Improved logging.
- Self-monitoring of LDAP sync status in Opsview.
- Support for multiple LDAP realms.
- Support for nested LDAP groups.
- Support for encrypted user secrets.
- For more information, see LDAP and Active Directory.
Required action
If using LDAP Sync, group files must now have an.xmlextension to be processed correctly.
- Improved
- Many dashlets have new optional columns available:
- Host address
- Host description
- Host group
- A new
CONFIGURECLUSTERpermission is now available that allows you to add empty clusters and manage them remotely. For more information, see Current role definitions. - The default message queue driver has been swapped from Kombu to Nucleon for all Python modules for performance improvements.
- Updated GPG key links for optimal security.
- The Opsview version is no longer displayed on the login page for unauthenticated users.
- Due to a bug in MySQL 5.7.41 and MySQL 8.0.32, the Opsview database user in MySQL 5 and MySQL 8 needs the
RELOADpermission. If you have a managed database, this is automatically added as part of the deployment upgrade. Once the issue is fixed in future versions of MySQL, this permission will be revoked. MariaDB databases are unaffected.
For more information, see What’s New in Opsview.
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Description |
|---|---|
| OP-49965 | Opsview now uses Nucleon as the default message queue driver for Python components, which can handle workloads with less resource usage. |
| OP-50915 | The window size has been adjusted so that you can better view the interface when performing SNMP polling. |
| OP-51662 | Added columns for Host Group, Host Description, and Host Network Address, and enhanced tooltips for:
|
| OP-53127 | Improved Uptrends integration allows you to view Uptrends data within Opsview. This includes real-time user monitoring and synthetic monitoring, both of which can be used to test and monitor the functionality of your website. |
| OP-53128 | When adding a new collector to a cluster without shell access to the Orchestrator, SSH tunnels can now be configured to allow all Opsview (collector-to-orchestrator) traffic to go over a single port. |
| OP-53145 | You can now access the Infrastructure Agent, allowing you to build your own agent from the source code and examine the source code to ensure it is secure and safe to use. |
| OP-54117 | Uptrends integration improvements:
|
| OP-54354 | Opsview Deploy installs a new Infrastructure Agent for self-monitoring while removing the old Opsview Agent automatically. NRPE checks now respect the NRPE_EXTRA_FLAGS variable. The following Opspacks have been updated:
|
| OP-55727 | The Infrastructure Agent supports existing Windows plugins, so when you switch to the newer Infrastructure Agent, the Windows plugins continue to function. |
| OP-56209 | Windows plugins now return the correct information when an error occurs or when expected arguments are passed. This allows you to monitor metrics on the Windows hosts, such as additional counters and services. |
| OP-56292 | A new CONFIGURECLUSTER permission is now available, allowing you to add empty clusters and manage them remotely. |
| OP-56692 | Updated Opspack: Opsview - Self Monitoring (v2.1.0). Added a new infrastructure self-monitoring host template to Opsview hosts. |
| OP-57023 | All service checks shipped with Linux builds of the Infrastructure Agent now contain help text describing all arguments and configuration instructions. |
| OP-57264 | Agent creates and uses self-signed certificate if no TLS options. |
| OP-57339 | Added host group, host description, and host IP column to dashlets and monitoring pages. |
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Description |
|---|---|
| OP-39297 | Improved opsview_sync_ldap script that is used for syncing Opsview users and roles with an LDAP or Active Directory server:
.xml extension to be processed correctly. Added Opspack: Opsview - Sync LDAP (v1.0.0) |
| OP-50697 | When a reload happens and a user is deleted but still has an open connection, the component now handles the error and delivers a new map without access. |
| OP-52840 | State Changes component no longer encounters message queue failures with the error message PRECONDITION_FAILED -- unknown delivery tag. |
| OP-55613 | Changed column headers when graphs are exported from:
|
| OP-56104 | Freshness Checker no longer leaks file descriptors when publishing stale result messages. |
| OP-56638 | The imported.yml file moved up one level into the cfg dir. |
| OP-56639 | Windows Agent runtime now works correctly when you add args to the runtime. |
| OP-57482 | No patch version is disclosed on the Opsview login page. |
| OP-57549 | The GPG key links have been updated. |
| OP-57551 | check_eventlog has been updated. |
| OP-57605 | Nucleon now handles configurable message_ttl_secs the same as kombu. |
| OP-57662 | Fixed an issue in the AF_INET error that was causing the Windows Infrastructure Agent to fail. |
| OP-57691 | Updated Opspack Application - Opsview to v3.0.4. The following Service Checks have been added to monitor the backup process:
|
| OP-57694 | For all supported OSes, the Capacity Planner plugin now returns both stderr if functioning properly and a non-OK state if no information is collected. |
| OP-57744 | MySQL 5.7 and 8.0 database backups now work correctly. |
| OP-57855 | When a restore fails, the audit log now shows the error message. The error details are now logged in the restore log, and the lock is released to make another attempt. |
| OP-57940 | Fixed an issue where incorrect ownership caused host checks from collectors to fail. |
| OP-58067 | After upgrading to a version with the new agent, self-monitoring checks are now working. |
| OP-58139 | When entering customer payload, the My System page no longer stops. Issues with field constraints have also been fixed. |
| OP-58182 | Infrastructure Agent script execution results can now hold at least 16KiB of data. To enable this functionality, set allow_multi_packet_response in the Agent configuration to true. |
| OP-58282 | When running checks with output longer than 4094 characters, Infrastructure Agent for Windows no longer times out. |
| OP-58325 | Upgrading from Opsview Agent to Infrastructure Agent no longer causes a version error message. |
| OP-58375 | The db_mysql now runs properly on every upgrade. |
| OP-58548 | Fixed an issue where the Opsview - Daily Backups service check went critical due to the filesystem backup tar exit code of 1. |
Opsview 6.8.0
Released: 25 January 2023
Highlights
These are the highlights of this release:
- Opsview now supports UTF-8 characters. For more information, see Supported Unicode Characters.
- The beta version of a new Windows and Linux infrastructure agent is now available to use and download at the Opsview Downloads website. For more information, see the Installation and operation documentation.
- Opsview Knowledge Center will make way for ITRS Documentation as our new documentation platform. Starting with the Opsview 6.8.0 release, you can find the documentation, including the ITRS Opsview Cloud Documentation, at ITRS Opsview Documentation. You can still visit the Opsview Knowledge Center for older versions of documentation, which will be available until further notice.
- Dashboard updates:
- The new Host Interfaces Dashlet dashlet in Dashboard can display the speed, throughput, discards, and error information for each interface configured.
- In Performance Graph, additional details are exported when saving graphs as images, with the ability to configure the graph balloon text format.
- In some configuration fields, the Metric Pie Chart supports wildcards (%).
- Top Services Issues supports wildcards (%) in some configuration fields, with the ability to summarize details for multiple services on the same host.
- Top Service By Metric supports wildcards (%) in some configuration fields, with a new bar chart display, Host Group, and Host IP columns.
- The Flow Collector processing now sets a timeout for reverse DNS lookups. This improves the response time for loading Flow Collector dashlets when the flow data contains IP addresses where reverse DNS is slow. To configure the timeout as well as the concurrency level for the reverse DNS lookups, see Advanced flow collector options.
- The Status - Performance Metrics endpoint now accepts the
include_hostgroupandinclude_hostipURL parameters. - VMware and HyperV virtual appliances no longer ship with the default SNMP community strings configured.
- Improved Netflow API security.
- The version of Golang used to build Opsview Monitor and associated plugins has been upgraded to 1.19.3 to improve security. As a result of this, support for legacy certificates has been removed from all Golang-based Opsview plugins. See Known Issues. All Golang components are now compiled using the updated toolchain:
- Opspacks
- timeseries-influx
- Registry (etcd)
- The following Opspacks have been updated to improve security:
- Application - HAProxy (v2.1.1)
- Application - Jenkins (v2.0.1)
- Application - RabbitMQ - Node (v3.0.1)
- Application - Varnish Cache (v2.0.1)
- Application - Varnish Cache 3.0 (v2.0.1)
- Application - Zookeeper (v2.0.1)
- Cloud - AWS - AutoScaling CloudWatch (v2.1.1)
- Cloud - AWS - CloudWatch (v2.1.1)
- Cloud - AWS - DynamoDB CloudWatch (v2.1.1)
- Cloud - AWS - EC2 CloudWatch (v2.2.1)
- Cloud - AWS - ELB CloudWatch (v2.1.1)
- Cloud - AWS - RDS CloudWatch (v2.2.1)
- Cloud - AWS - Route53 CloudWatch (v2.1.1)
- Database - Etcd (v2.0.1)
- Opsview - Component - Datastore (v4.1.2)
- Opsview - Component - Load Balancer (v4.1.2)
- Opsview - Component - MessageQueue (v4.1.2)
- Opsview - Component - Registry (v3.0.2)
For more information, see What’s New in Opsview.
| 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. Upated Opspacks:
|
| OP-55866 | Initial UTF-8 support includes using scandic characters. Upated Opspacks:
|
| 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
Highlights
Released: 2 November 2022
These are the highlights of this release:
- A new agent for Windows and Linux based machines is now in closed beta. If you are interested in taking part in this closed beta, please reach out to either Customer Support or your account manager.
- A new Network Topology permission
NTVIEWALLhas been added which, when applied to a role, allows a user to view any unimported nodes in the network topology map. Also, two known issues related to Network Topology have been resolved to improve security. - The Events Viewer, Notifications, and Graph Center pages have access to new preset time durations. These are:
last full day— last full 24 hour period (00:00 to 00:00).last full 7 days— last 7 full 24 hour periods (00:00 to 00:00).last full week— last full week, for example if used on Tuesday, this would be the previous Monday to Sunday.last full month— last full month, for example if used on February 2, this would be January 1 to 31.
- 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 and 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 and sflow.
- Added the ability to select historical time ranges to the following dashlets:
- Performance Graph
- Receivers Protocol Trend
- Transmitters Protocol Trend
- Added a new Dashboard Time Range Sync mode to sychronise cursors and zooming across supported dashlets.
- 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 and shortcut (edit report view)
- The
opsview-flow-collectorcomponent has been made more resilient to any messagequeue failures, so it now reconnects automatically. TTL (time to live) has been added to any flow requests made through the REST API, so messages are 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. Additional timing data will be returned by Flow REST API calls, for debugging:collector— machine ref for the collector that has run this flow request.duration_total— total time spent running the call on the remote collector.duration_nfdump— time spent by the call running the nfdump command.
For more information, see What’s New in Opsview.
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-54616 | Added Capacity Planner integration Opspack using OLD Windows and Linux agents. |
| 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
Highlights
These are the highlights of this release:
- ITRS Uptrends is 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
- It is now possible to deploy Opsview to collectors using sudo without the
NOPASSWDoption 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 thesshd_configon the collector.The following playbooks will now set up the appropriate version of Python on InfluxDB systems if configured, as the first action in a deployment:Match User <local user for sudo> PasswordAuthentication nocheck-deploy.ymlsetup-hosts.yml
- Re-notifications are now consistently sent following configuration changes. In previous versions of Opsview Monitor, 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.
For more information, see What’s New in Opsview.
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).
["Opsview"]
["Release Notes"]