Documentation forHybrid Cloud Observability

SolarWinds Hybrid Cloud Observability 2024.2 release notes

Release date: June 4, 2024

Here's what's new in SolarWinds Hybrid Cloud Observability 2024.2.

SolarWinds Hybrid Cloud Observability runs on the SolarWinds Platform.

New features and improvements in Hybrid Cloud Observability

SolarWinds Hybrid Cloud Observability 2024.2 includes the new features in version 2024.2 of the SolarWinds Platform. For more information, see the SolarWinds Platform 2024.2 Release Notes.

Cloud monitoring support for Azure SQL databases

Hybrid Cloud Observability now supports cloud monitoring for Azure SQL databases. Discover, poll, and drill down into the details of Azure SQL DB instances within the context of other Hybrid Cloud Observability-monitored entities and devices.

Cloud monitoring support for Azure load balancers

Hybrid Cloud Observability now supports discovering, polling, and monitoring Azure load balancers. Monitor the status, main attributes, health scores, and metrics for Azure load balancer instances.

Updated cloud dashboards

Dashboards for cloud entities, including Network and Storage dashboards for Azure and the summary dashboard for AWS have been updated with modern and refreshed UI elements that better organize and summarize your monitored cloud entities.

Network monitoring support for Aruba Wireless Access Points

Add Aruba Central orchestrator wireless access points for monitoring and use the following insights to secure efficient wireless network management:

  • Wireless network strength: keep track of the overall count of access points deployed in your network, monitor the number of connected users, or detect and manage unauthorized access points by evaluating the signal strength.

Network monitoring support for Aruba Silver Peak SD-WAN

Add Aruba Silver Peak SD-WAN orchestrator nodes for monitoring and pair the Aruba orchestrator with edge nodes. Monitor the inventory, such as orchestrators, sites, or edge routers, SLA classes/profiles, interfaces, tunnels, applications/SLA paths. Observe the SD-WAN performance by monitoring SLA, such as jitter, latency, or packet loss. See Monitor SD-WAN for Aruba orchestrators with Hybrid Cloud Observability.

Aruba SD-WAN monitoring uses API-based polling. See API-based monitoring for Aruba SD-WAN devices for details.

Flexible sizing of High Availability Pools for Additional Polling Engines

For Additional Polling Engines (APE), you can now define High Availability (HA) pools greater than two via the API. This allows a single or multiple APEs to serve as the fail-over for multiple APEs.

SolarWinds recommends configuring a ratio of one backup polling engine to four active polling engines. With this configuration, you can decrease the server footprint to run Hybrid Cloud Observability and lower administrative and Windows licensing costs. See Set up High Availability pools with multiple active and standby servers.

Support for new devices in the vulnerability and risk dashboard

The following device types are now supported in the vulnerability and risk dashboard:

  • PaloAlto

  • Fortinet

  • HPE-Aruba

Specify the SSH encryption algorithms used for a device type in the device template

You can use the device template to specify what SSH encryption algorithms Hybrid Cloud Observability uses when communicating with a device. The encryption algorithms that you specify must be supported by the devices that use the device template, and they must be supported by Hybrid Cloud Observability.

For information about supported algorithms, see Supported algorithms and ciphers for SSH communications. For information about specifying the SSH algorithm in a device template, see NCM device template commands.

Credentials for each polling engine

To write to network share or to specify a custom location for saving certain things (such as downloaded configs or NCM job results), you must give NCM write access to the network share or custom location. You can now specify different credentials for each polling engine. You might want to do this because:

  • No single set of credentials is valid for all polling engines to access the location (for example, the polling engines are in different domains).

  • You can specify local credentials for each polling engine. As a result, when you specify various custom locations, you can specify any custom location that the polling engine's local credentials have access to.

CPE match data feed URL

The CPE match data feed URL is now specified on the Firmware Vulnerability Settings page. In previous versions, this URL was specified in Advanced Configuration settings.

The CPE match data feed provides the product or platform applicability statement to CPE URI matching based on the CPEs in the official CPE dictionary. This is the same information displayed on the NIST website when you expand the matches for a match criteria.

Increased visibility for tag actions

Tag actions can be viewed as a list in the Add an action wizard without hovering your cursor over the action.

DHCP/DNS wizard improvement

The DHCP/DNS wizard has a new interface for scope splitting along with additional user workflow improvements.

Reports management enhancement

EOC can now query reports from remote instances and filter them by site and by custom properties.

Other improvements

  • Topology calculation process was updated to improve performance.
  • You can poll VeloCloud traffic interface data using a private MIB.

Return to top


Case number Description

The failover functionality on Windows Server 2022 works correctly.

01555171, 01611265, 01574171

*When you run the Configuration Wizard using an existing Windows or Azure Active Directory account, the Infoblox Server credential test no longer fails with the following message:

Could not load file or assembly 'System.Text.Json

00837847, 01457151, 01253910

Changes were made to prevent database performance issues in large environments.


If SQL Server stops a SQL process, LA database maintenance logs the issue and continues running instead of waiting indefinitely on the process.

01498395, 01505412, 01509365, 01522260, 01527757, 01534554, 01535156, 01544402, 01583022

When devices include duplicate data, inventory jobs no longer fail with the message Violation of PRIMARY KEY constraint 'PK_NCM_Entity_Logical'.

01496355, 01535319, 01535948, 01541480, 01543568, 01544631, 01564617, 01565311, 01571856, 01579695

Additional ciphers are supported for collecting data via SSH. This fixes the connectivity issues with certain versions of the FortiGate software. For the list of supported ciphers, see Supported algorithms and ciphers.

If NCM still cannot connect to Fortigate devices after the upgrade, complete the additional steps in this article.


Having duplicate names for the same node ID no longer causes an upgrade to fail.


When you display shadowed ACL rules, line numbers are no longer broken across multiple lines, making them difficult to read.


Upgrades no longer fail with the message Error while executing script - ALTER TABLE DROP COLUMN failed because column 'InterfaceID' does not exist in table 'NCM_ARPTables'.


Config change approval requests are no longer deleted because of account limitations.

01376614, 01430014, 01497551

If the CVE field on the Firmware Vulnerabilities Settings page contains the CPE match data feed URL instead, a message is displayed and the settings cannot be saved.

01490187, 01398440

The Collector service no longer reports errors related to SwitchStack UNIQUE KEY constraints, similar to:

ERROR SolarWinds.Collector.DataSynchronization.InventoryManager - SyncEntity for SSM:53 failed: System.Data.SqlClient.SqlException (0x80131904): Violation of UNIQUE KEY constraint 'UK_NPM_SwitchStackMember'. Cannot insert duplicate key in object 'dbo.NPM_SwitchStackMember'. The duplicate key value is (965, FOC2327T1DZ)

01526717, 01572246

Interface traffic for VeloCloud Networks is polled correctly.

The common MIB2 ifHCxxoctets counters do not work consistently for VeloCloud Edge devices when the device is configured as an HA (high availability) pair and its current state is StandBy. To overcome this issue, SolarWinds implemented a custom VeloCloud interface traffic data SNMP poller for getting OutTotalBytes/InTotalBytes counters from a private VeloCloud MIB.


When retrieving information about Meraki SD-WAN tunnels, all VPN statuses for an organization are retrieved, even when there are more than 300.

01560284, 01574209, 01579279

A new MAC property for Device Studio Node Details pollers allows specification of the data source (OID) for MAC address collection. With this change, custom node detail pollers that were created in 2023.4 or earlier work correctly, and you can set the MAC data source for them.


Empty DNS field in the DB NodesData table for Viptela, VeloCloud, and Aruba orchestrators no longer causes polling to fail, and an error is no longer displayed similar to:

ERROR SolarWinds.Orion.Pollers.Framework.PollerBase - Failed to poll Viptela Orchestrator with Node ID=7: System.ArgumentException: ipAddressOrHostname


In Centralized Settings, the new setting SendBgpInfoRequests has the following values:

  • True: Sends requests to retrieve BGP Annoucement and WHOIS network data.
  • False: Stops sending these requests. Only stored data is used.

Use this setting to temporarily stop requests if the NetPath_Networks table is filled during BGP polling and you see errors such as:

ERROR SolarWinds.NetPath.Bgp.RawClients.RawClient - (null) [Flow 40442] TcpQueryAsync have failed. Endpoint: Unspecified/ Exception: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.


The Wireless Heat Map editor displays the owner information correctly.


Wireless heat map generation no longer fails when some access points return invalid data. The heat map generates, but problematic access points are ignored.


The performance of SD-WAN charts on the SD-WAN Orchestrator Details view has been improved.


If a custom property has a NULL value for some nodes and an empty string for other nodes, polling with a Universal Device Poller (UnDP) and then sorting by the custom property no longer returns an error message.

01509390, 01559294

When you edit a group, saving the Add & Remove SolarWinds Platform Objects page without making any changes no longer removes any existing objects.


Detection of L3 Next Hop connections for VPN tunnels has been improved. Previously, having a full L3 Interface-to-Interface connection required that both nodes reported valid Next Hop addresses for each other. Now, only one node needs to report the connection. This default behavior can be changed with the advanced configuration option ResolveTargetInterfaceForNextHop.

00465823, 01472478

A server without an IP address does not cause the List of Virtual Servers widget to display an exception.


SolarWinds IP address and port pollers no longer return misleading results for Meraki appliance models that have a fallback cellular uplink.


Queries associated with the Duplex Mismatch alert have been tuned to improve the performance of the SolarWinds Platform Web Console.

01040126, 01155575

If one IP address has more than RemoteSystemName in LLDP data, inaccurate connections are no longer reported in the topology table.

01564091, 01573720

*VeloCloud VPN Tunnel statistics are calculated correctly, regardless of the statistics collection interval and the poll interval settings.


*When two NetPath services on different probes have the same name, logs no longer contain the message Updating members snapshot for container.


In previous versions, even though a user had the right to manage nodes and could add new devices or edit existing ones, the user was not able to add an interface through the NetFlow Events resource. Now, users with Node Management rights are able to add interfaces. Admin rights are no longer required for this task.


During on-demand DNS resolution, when an option to resolve IP addresses is disabled and then reenabled after maintenance, IP addresses are resolved and the Domains and Resources widgets display the correct information.

01440937, 01512489

Creating and managing an application with a large port range is handled properly in NTA.


Netflow PDU is marked as malformed when octets or packets have a negative value, fewer octets than packets are reported, and maximum transition unit (MTU) is larger than 64. These types of invalid data are detected and discarded.


When you enable the High Receive Percent Utilization with Top Talkers out-of-the-box alert or High Transmit Percent Utilization with Top Talkers out-of-the-box alert and configure an alert action to send a PDF, the PDF file is generated correctly and it no longer contains an error similar to:

Unexpected Website Error Failure parsing NetObject key.


An API poller that includes a null value no longer causes sent requests to fail with the message Bad Request.

01379396, 01592659

When Windows Update Monitoring fails to connect to a remote server, the correct message is displayed instead of a message saying that initial polling is in progress.


An API poller can be removed using the SWIS SDK. The Delete command no longer returns an error.


Running Asset Inventory on a node with the Linux agent installed no longer fails with errors such as the following:

Failed to parse or validate SNMP parameters provided by user


When an Exchange user's password includes a special character, AppInsight for Exchange displays the correct data for Custom PowerShell Monitor components, rather than showing them in an unknown state.

00596630, 01436136

A VM in an Azure account is polled correctly, and the status is not shown as unknown.


A SolarWinds query to retrieve component statuses was tuned to run more quickly.


The performance of the Last 10 Events widget has been improved.


Non-admin users have access to the new Azure dashboard.


When a custom property with the entity type Application is initially saved without any values, the custom property can be used for filtering on the Manage Application Monitors page.


When you add a node and enter WMI credentials without specifying the domain, Windows update polling is successful and the Windows Update Information widget no longer contains an error message.


*When an AppInsight for SQL application is created using the SWIS verb CreateApplication, all settings are saved correctly.

01510807, 01542783, 01596899, 01605745

*When the job ID and the account ID do not match, adding a cloud account no longer fails with messages such as the following:

Create failed, check fault information. The INSERT statement conflicted with the FOREIGN KEY constraint "FK_CLM_SelectedCloudRegions_CloudJobSettings". The conflict occurred in database "SolarWindsOrion", table "dbo.CLM_CloudJobSettings", column 'Id'. The statement has been terminated.

Update failed, check fault information. Value cannot be null. Parameter name: uri


*When custom properties with the entity type Application are initially saved without any values, after editing an application, the edited application is displayed as expected on the Manage Application Monitors page.


When you add a node and enter WMI credentials without specifying the domain, Windows update polling is successful and the Windows Update Information widget no longer contains an error message.


Running Asset Inventory on a node with the Linux agent installed no longer fails with errors such as the following:

Failed to parse or validate SNMP parameters provided by user


Ports that are administratively shut down are not imported if this option is deselected in the discovery.

01392778, 01400254

The MAC addresses of devices connected to Fortiswitches are displayed correctly.


The version of OpenJDK shipped with the product has been upgraded to 11.0.22.

01283241, 01505280, 01526330

Nutanix Hardware Health polling works in large environments.

01456785, 01524861, 01544639

Free nodes are no longer included in license consumption when adding a new virtual environment.


VMAN polling now collects reboot values for hosts during the sample collection (every 10 minutes), which enables the Host Rebooted alert to work correctly.


The Node Details widget for aVMware ESX server shows the correct number of CPUs.


Nutanix Controller VM (CVM) credentials can be added to Nutanix Clusters.


The Save new credentials button is disabled during credentials validation, so you do not run the same verification multiple times.


*The Node Details widget on the Node Details page displays the correct value for Number of Cores instead of N/A.

In previous versions, the Number of Cores field was labeled No of CPUs.

01470768, 01487037, 01497412, 01498672, 01500547, 01501808, 01502346, 01504377,01505255, 01519189, 01519623, 01525710, 01525762, 01526225, 01534998, 01540646, 01541028, 01546443, 01591264

Database maintenance no longer fails with the following message:

Violation of PRIMARY KEY constraint 'PK_VoipOperationStdDevResults_Hourly'. Cannot insert duplicate key in object 'dbo.VoipOperationStdDevResults_Hourly'.


Polling Cisco CallManagers with attached gateways does not increase CPU usage or produce an error.

01517771, 01542771, 01561622, 01562558

The Business Layer on an additional polling engine no longer fails to start with the following message:

BusinessLayer.Plugin (null) - IP SLA Monitor service [SW550SLRWPA037] failed to start.System.ServiceModel.FaultException1[System.ServiceModel.ExceptionDetail]: An item with the same key has already been added.


The VNQM business layer on the additional polling engine no longer times out when receiving license information from the main polling engine in environments with many nodes.

01485538, 01528554

CDR data is processed when columns contain Cisco-specific call termination cause calls, and an error is no longer displayed, similar to:

ERROR BusinessLayer.Task.CdrCmrCsvFileReader (null) - Cannot convert int value [column:destCause_value,rawValue:2751463455]“. As a result, this call data is not saved to DB.

Also, the VoIP Call Details resource is rendered correctly on the Call Details page, and the VoIP Search page opens without errors.

01542771, 01561622, 01562558,

An issue that could cause menu failures or prevent IP SLA from loading has been fixed.

01327448, 01469467, 01491596, 01496347, 01503660

VNQM no longer displays invalid messages saying that the license limit is exceeded. This was caused by attempts to verify licenses before they were loaded.


The Last Polled field on the Call Manager page now displays the time in the time zone of the server, not in the UTC time zone.

01475848, 01487847

Juniper RPM operations are polled and the status changes correctly.


When an Avaya call manager has a large number of phones, gateways, and other attachments (for example, over 1,000), polling is completed during one polling cycle.


Integration with third-party FTP server software has been improved. VNQM can download call manager data from FTP servers such as FileZilla and others.


IP SLA UDP Jitter operations are no longer deleted from VNQM if it is created with an external node as a target.


*The Network Service Assurance Operations with Issues widget displays data correctly, rather than displaying this message:

There was an error rendering Network Service Assurance Operations with Issues

01560713, 01573179, 01589368

*VNQM no longer generates a large number of Out of Memory exceptions when working with the job engine.

01584394, 01589368, 01592893

*In large environments, timeouts no longer occur frequently during discovery operations.

01238012, 01596373, 01593165, 01597616

*In large environments, SQL deadlocks no longer occur frequently when the VoipCdrs table is accessed.

*This fix was added after the RC release.

Installation or upgrade

For new SolarWinds Platform deployments, download the installation file from the Hybrid Cloud Observability product page on or from the Customer Portal. For more information, see Get the installer.

To activate Hybrid Cloud Observability in an existing SolarWinds Platform deployment, use the License Manager.

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.

For supported upgrade paths to 2024.2, see Upgrade an existing deployment.

Return to top

Known issues

Errors in the IP SLA business layer log file

When trying to poll and save new types of operations not previously collected, errors appear in the IPSLA business layer log file.


Restart the SolarWinds Orion Module Engine service and the SolarWinds Job Engine v2 service.

End of life

Version EoL announcement EoE effective date EoL effective date
2022.4 June 4, 2024: End-of-Life (EoL) announcement – Customers on Hybrid Cloud Observability 2022.4 should begin transitioning to the latest version Hybrid Cloud Observability. July 4, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Hybrid Cloud Observability 2022.4 will no longer be supported by SolarWinds. July 4, 2025: End-of-Life –SolarWinds will no longer provide technical support for Hybrid Cloud Observability 2022.4.
2022.3 February 6, 2024: End-of-Life (EoL) announcement – Customers on Hybrid Cloud Observability 2022.3 should begin transitioning to the latest version Hybrid Cloud Observability. March 7, 2024: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Hybrid Cloud Observability 2022.3 will no longer be supported by SolarWinds. March 7, 2025: End-of-Life –SolarWinds will no longer provide technical support for Hybrid Cloud Observability 2022.3.
2022.2 November 1, 2023: End-of-Life (EoL) announcement – Customers on Hybrid Cloud Observability 2022.2 should begin transitioning to the latest version 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 supported by SolarWinds. December 1, 2024: End-of-Life –SolarWinds will no longer provide technical support for Hybrid Cloud Observability 2022.2.

See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier Hybrid Cloud Observability versions, see Hybrid Cloud Observabilityrelease history.

Return to top

Deprecation notice

The following platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms, and avoid using deprecated features.

Type Details
MAPI User Experience Monitor MAPI User Experience Monitor, a component monitor that can be added to an application template, is deprecated as of SAM 2024.2. It is still available and supported in the current release, but will be removed in a future release. Deprecation is an indication that you should avoid expanded use of this feature and formulate a plan to discontinue using the feature.

Return to top

Legal notices

© 2024 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.


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.