Release date: November 1, 2023
Here's what's new in SolarWinds Hybrid Cloud Observability 2023.4.
SolarWinds Hybrid Cloud Observability runs on the SolarWinds Platform.
- See the Hybrid Cloud Observability 2023.4 system requirements.
- For information about working with Hybrid Cloud Observability, see the Hybrid Cloud Observability Administrator Guides.
New features and improvements in Hybrid Cloud Observability
For information about new features and fixes in the SolarWinds Platform, see the SolarWinds Platform 2023.4 Release Notes.
New Vulnerability Dashboard and Risk scorecard
This release introduces a new vulnerability and risk dashboard, available for Hybrid Cloud Observability Advanced users. View vulnerability and risk severity, determined by imported CVE information from CVEs based on CVSS v3. Schedule CVE data imports, and match CVE information to individual nodes. See calculated risk scores for individual monitored nodes and an aggregated risk scored for your environment.
Platform Connect supports more device types
Platform Connect now supports sending information for more device types to SolarWinds Observability, including application and virtualization.
Greater visibility for simplified SD-WAN monitoring
Real-time Tunnel and WAN metrics like service provider, packet loss, latency, and jitter are now available for use in dashboard widgets and PerfStack for Meraki, VeloCloud, and Viptela SDWAN devices.
Anomaly Based Alerts improvements
Anomaly Based Alerts now includes a new visual representation of the normal operating range (NOR) of a device’s metrics. The entity detail page contains NOR charts for every observed metric present for the entity that is triggering an Anomaly-Based Alert.
You can now define anomaly-based alerts for virtualization entities. See the list of supported entities with their metrics below:
AlertStack is now available under the “Alerts and Activities” menu.
The AlertStack cluster detail page now supports filtering of occurrences together with maps. Occurrences can be filtered based on the Status and Element Type. Accordingly, the map nodes reflect this filtering as well.
AlertStack now supports creation of incidents in SolarWinds Service Desk (SSD) for AlertStack clusters. This action can be done for clusters in open or suspended states only.
For information about new features and fixes in the SolarWinds Platform, see the SolarWinds Platform 2023.4 Release Notes.
|01189602, 01296329, 01268284||
In deployments with additional polling engines (APEs), attempting to integrate the SolarWinds Platform with DPA would install the DPA Business Layer on the APE. This caused problems with the DPA integration, including:
|01231016||When custom properties used in alerts are created in a different SolarWinds Platform product, the associated column in the All Active Alerts page in EOC is not blank.|
When you run a report that queries the SolarWinds log database, the results of the query are shown instead, not the message
In a large, complex environment, network configuration management jobs and inventory jobs run as expected.
Network configuration management jobs no longer make unnecessary APE license checks, which were causing the jobs to run slowly.
|00837847, 01358148, 01426785||
Inventory collection was updated to prevent database blocks, which were affecting performance.
|01352472||If you run a job that saves the results of a policy report to a file, and the file name includes a macro, the macro is parsed correctly and the report's content and formatting are accurate.|
|01336072||When SolarWinds high availability (HA) is deployed, a network configuration search performed after a failover includes all configs. The search is not limited to only the most recently downloaded configs.|
A vulnerability that could expose a password has been fixed.
A misspelled word in INFO messages in the
The Config Details page shows the downloaded time based on the SolarWinds Platform time zone, not UTC time.
When an inventory job retrieves a large Flash Size value, it records the value correctly and no longer returns the following error:
Real Time Change Notification works as expected when the IP address provided to it is not the primary IP address for the node.*
|01428683, 01330623, 01349629||
In 2023.2, the default timeout value for
|01295129, 01350421, 01428125||
When the SolarWinds Platform is configured to use Windows authentication, running interface percentile traffic reports no longer returns an error.
If an interface name includes special characters, the special characters are no longer escaped on the Interfaces with High Percent Usage (no paging) resource. This behavior was preventing database maintenance from running as scheduled.
The load time for the Interface Availability widget has been significantly decreased.
By default, network discovery enables all pollers on a device. So, if a topology poller is disabled on the List Resources or Manage Pollers page, it is enabled again when network discovery runs. A new advanced configuration option is available to enable you to override this default behavior. If do not want certain topology pollers to be enabled when network discovery runs:
|01348970, 01350142, 01361854, 01362953, 01420814, 01430172||
Out-of-the-box Switch Stack alerts can be copied and edited, and they are triggered as expected.
Universal Device Poller gauges load without errors and performance is improved.
If application data is corrupted, the Manage Applications and Service Ports page no longer attempts to list the applications. Corrupt data does not prevent the page from opening with the following message:
Additionally, a daily maintenance task detects and removes any corrupt application data.
If a user without permission to view NetFlow data attempts to access a NetFlow page, permissions are evaluated and the
A change to the NetFlowInterfaceSources_Metadata table in the SolarWinds Platform database prevents deadlocks in environments with a large number of VMware devices.
|01400259, 01419304, 01420644||
If a deployment includes more than one application template with the same name, the Configuration Wizard no longer fails with the following error:
|01360008, 01379355, 01390806, 01399847, 01400259||
The SolarWinds Platform Web Console no longer becomes unresponsive or stops functioning due to missing keys in the cloud monitoring resource file.
On the Node Details Summary page, when you click Real Time Event Viewer and then click the Message column for an event, the Message Details popup opens as expected.
When you add a node with Microsoft SQL Server 2022 deployed, AppInsight for SQL is discovered.
|01290468, 01305182, 01317562, 01320352, 01320666||
During upgrades data from old tables is migrated successfully and the obsolete tables are removed. In a previous version, incomplete data migration could cause issues such as:
|01183556, 01337907, 01353375, 01389703||
If the Configuration Wizard fails during an upgrade, attempting to rerun the wizard no longer fails with the message
When a problem occurs with the API poller, the following message was improved to provide more information about the cause of the problem:
|01142194, 01357225, 01438644||
When a node is deleted or unmanaged, Application Dependency Mapping (ADM) polling does not continue for that node. In previous versions, continuing to poll a deleted or unmanaged node for ADM data caused the ADM_ProcessingQueue table to become very large.
Long status messages associated with an application monitor are displayed correctly after an upgrade.
Alerts on API Pollers that should be triggered when the response time exceeds a threshold are no longer triggered when the response time is below the threshold.
If ADM polling is disabled for the SolarWinds Platform, the node detail page does not display the Application Dependency Polling Enabled check box.
If AppInsight for IIS runs for long periods, the APM_IisBb_Request_Detail table no longer grows without limits, causing performance issues.
The CreateApplication verb in SWIS for the AppInsight for SQL template now works when you are using a remote node and database. Issues with credentials and connection testing have been resolved.
The default poll no longer fails when more than one array is in a Nimble cluster.
The Vserver Status widget and the Vservers on this Cluster widget now show the same Vserver capacity data.
The Ethernet Ports Used Over Time now shows data for the selected time period instead of only the data for the current day.
When a wireless node is discovered with UDT port monitoring enabled and devices from the node are added to the Watchlist, the Watchlist widget no longer displays type conversion errors such as:
The Port Details widget now displays the MAC address, IP address, or Hostname for all devices.
|00570890, 00582046, 00717223||
The All User Log Ins widget displays data about the currently open endpoint, not the first endpoint that was opened.
|01314714, 01333769, 01351695, 01365630, 01365850, 01382555, 01398156, 01412701, 01420009, 01426518, 01436135||
The Port Details widget displays IP addresses even if the VLAN port is not monitored.*
|01308188, 01332779, 01380614, 01382170, 01396520, 01404094||
When a node uses automatic private IP addressing (APIPA), the vendor and machine type are reported correctly.
Database maintenance no longer fails with the following message:
The bulk insert query no longer runs slowly and causes performance issues on the database.
The Calls by Region widgets display the correct data.
IP SLA operations function correctly, and the
The FTP server is no longer filled with failed files, and VoIP views displays call manager information correctly.
After a call manager is removed, any associated CDR files are no longer processed, which prevents putting an unnecessary load on the FTP server.
Call managers are polled only by the assigned polling engine, not by all polling engines.
When CDR files for different call managers are stored in separate folders on the FTP server, CDR files for all call managers are processed. VNQM no longer ignores CDR files for all call managers except the last one added.
Avaya Call Manager now shows the correct numbers of phones.*
Avaya RTCP data is collected and displayed as expected. Logs no longer include errors associated with the UTC offset.*
A large number of CDR or CMR files on the FTP server no longer cause an out of memory exception.*
*This fix was added after the RC release.
Installation or upgrade
For upgrades, go to Settings > My Deployment to initiate the upgrade. The SolarWinds Installer upgrades your entire deployment (all SolarWinds Platform products and any scalability engines).
For more information, see the SolarWinds Platform Product Installation and Upgrade Guide.
Before you upgrade!
If you are upgrading from a previous version, be aware of the following considerations:
Upgrading from Orion Platform 2020.2.6 or older -
- Before upgrading from Orion Platform 2020.2.6 and earlier to SolarWinds Hybrid Cloud Observability, check the SolarWinds Platform release notes for additional information.
End of life
SolarWinds recommends you upgrade to the latest version of your products at your earliest convenience.
|Version||EOL Announcements||EOE Effective Dates||EOL Effective Dates|
|2022.2||November 1, 2023: End-of-Life (EoL) announcement – Customers on Hybrid Cloud Observability 2022.2 should begin transitioning to the latest version of Hybrid Cloud Observability.||December 1, 2023: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Hybrid Cloud Observability 2022.2 will no longer be actively supported by SolarWinds.||December 1, 2024: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Hybrid Cloud Observability 2022.2.|
|2020.2.6||April 18, 2023: End-of-Life (EoL) announcement – Customers on Hybrid Cloud Observability 2020.2.6 should begin transitioning to the latest version of Hybrid Cloud Observability.||May 18, 2023: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Hybrid Cloud Observability 2020.2.6 will no longer be actively supported by SolarWinds.||May 18, 2024: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Hybrid Cloud Observability 2020.2.6.|
© 2023 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.