Here's what's new in SolarWinds Observability Self-Hosted 2023.2. You can find the applicable system requirements here.

To view release notes, system requirements, and product guide PDFs for supported versions of SolarWinds Observability Self-Hosted, see SolarWinds Observability Self-Hosted previous versions. To view release notes for multiple versions and multiple SolarWinds Platform products on a single page, see the release notes aggregator.

 

Attention 2023.2 customers

If you are upgrading from a previous version, be aware of the following considerations.

Upgrading from multiple module license keys to a single SolarWinds Observability Self-Hosted license key

• If you received multiple module keys when you purchased SolarWinds Observability Self-Hosted, after upgrading to the current version, get your SolarWinds Observability Self-Hosted license key from the customer portal and then activate it in the SolarWinds Platform. This will disable your current module license keys.

Upgrading from Orion Platform 2020.2.6 or older

• Before upgrading from Orion Platform 2020.2.6 and earlier to SolarWinds Observability Self-Hosted, check the SolarWinds Platform release notes for additional information.

New features and improvements in SolarWinds Platform

Security improvements

• Security improvements for external alert actions. Only users with server admin rights are able to create new external actions. See Approve alert actions executing a script.
• SMTP authentication improvements
• SSH security improvements

New features and improvements in SolarWinds Observability Self-Hosted Essentials

The following features are exclusive to customers with a SolarWinds Observability Self-Hosted license.

Additional improvements to Cloud Discovery and Monitoring

For AWS and Azure monitoring, you can now select AWS and Azure entity tags as a filter for selecting entities during Cloud Discovery. Using tags is now supported for virtual machines, their attached volumes, and DNS zones. In addition, Virtual network gateway monitoring, Virtual private cloud (VPC) monitoring, and site-to-site monitoring are now also available for AWS. Information about subnets is now also shown in the Cloud Instance Details page for both AWS and Azure.

Status-only nodes

Up/Down status monitoring for ICMP nodes and external nodes no longer consumes a node from your SolarWinds Observability Self-Hosted license when no additional monitoring has been assigned to them. A Node License Summary report which shows the number of ICMP/External nodes without external monitoring assigned is now available.

Server node support for Anomaly-Based Alerts

Anomaly-Based Alerts can now be defined for use with Linux and Windows servers, which now appear in the server filter during the entity selection step of the Anomaly-Based Alert creation flow. The supported metrics are CPU, memory, response time and packet loss. Windows workstations are not supported.

VPC monitoring

Virtual network gateway monitoring, Virtual private cloud (VPC) monitoring, and site-to-site monitoring are now also available for AWS. Information about subnets is now also shown in the Cloud Instance Details page for both AWS and Azure.

VeloCloud token authentication

You can use an API token generated in the VeloCloud administration to poll VeloCloud data from the orchestrator. See Add VeloCloud orchestrator for details.

Token-Based authentication for F5 iControl

When you specify credentials for polling F5 nodes via iControl, the credentials are used for retrieving an API token. The token is further used for identification. Using API tokens for authentication improves both security and performance.

API for SAM credentials

The common Credentials API now supports API Poller credentials.

Cloud Monitoring

Virtual network gateway monitoring, Virtual private cloud (VPC) monitoring, and site-to-site monitoring are now also available for AWS. Information about subnets is now also shown in the Cloud Instance Details page for both AWS and Azure.

For additional improvements, see the SolarWinds Platform Release Notes.

Improved performance of APM DynamicEvidence

As part of performance improvements, the APM_DynamicEvidence_DetailData table has been removed. The new APM_DynamicEvidence_Current table contains the last value for both numeric and string values including the row and schema id. As a result of this change, scripts referencing the APM_DynamicEvidence_DetailData table will no longer work.

Device view integration

You can view all the telemetry UDT provides for your interfaces on the NPM Device view.

Support for Cisco Unified Communications Manager 14

As of version 2023.2, VNQM supports Cisco Unified Communications Manager (CallManager) 14.

New features and improvements in SolarWinds Observability Self-Hosted Advanced

Customers with a SolarWinds Observability Self-Hosted Advanced license receive all Essentials updates, plus the following features exclusive to Advanced customers.

Firmware vulnerability matching for Cisco IOS XE and IOS XR devices

NCM 2023.2 alerts you if managed Cisco IOS XE and IOS XR devices (in addition to other Cisco IOS devices) could be affected by firmware vulnerabilities reported by the National Institute of Standards and Technology (NIST).

In September 2023, NIST will retire its legacy data feeds and distribute firmware vulnerability data through application-programming interfaces (APIs). An upcoming release of NCM will be modified to adapt to the changes.

Special characters in macros can be escaped in policy rule searches

In previous versions, policy rules could not search for the name of a macro, such as ${AgentIP}. If a search string included ${AgentIP}, NCM compiled the macro and searched for the node IP address instead of the string ${AgentIP}.

In NCM 2023.2, you can use \ to escape the curly braces (for example, $\{AgentIP\}) to search for the name of a macro.

New virtual cloud monitoring options

Virtual network gateway monitoring, Virtual private cloud (VPC) monitoring, and site-to-site monitoring are now also available for AWS. Information about subnets is now also shown in the Cloud Instance Details page for both AWS and Azure.

Fixed CVEs

At SolarWinds, we prioritize the swift resolution of CVEs to ensure the security and integrity of our software. In this release, we have successfully addressed the following CVEs.

Fixed customer issues

Case number	Description	Platform product
1286152, 1288976, 1289910, 1290594, 1291107, 1297401, 1307087	The issue where date and time in custom reports did not match the format specified in Time Period was addressed.	Platform
396114, 532706, 760265, 898102, 910698, 965970, 1049100, 1190709, 1199690, 1205029, 1206699, 1248892, 1257590, 1280347	The issue where database maintenance was failing after the upgrade was addressed.	Platform
1121180	The issues with Azure Cloud Details views were addressed.	Platform
1232029	Removed SolarWinds Platform Agent plugins are marked for uninstallation after the upgrade.	Platform
1289446	The issue where SolarWinds Administration Service read and wrote the package type to an incorrect registry path was addressed.	Platform
1272370, 1273749	The issue where importing alerts with SQL macro variables was blocked for Admin users was addressed.	Platform
842639	The issue where time zones of SQL server and SolarWinds Platform polling engines showed a warning even when the zones were the same was addressed.	Platform
1052957, 1240424, 1245960, 1246538, 1256606, 1257671, 1266763, 1276328, 1267382, 1279002, 1280926, 1281291, 1283928, 1288216, 1290612, 1291755, 1295777, 1296218, 1297821, 1297859	SolarWinds Information Service performance issues when users without admin rights use PerfStack were addressed.	Platform
1270128	The issue where the Configuration Wizard failed when configuring the website because of an applicationHost.config error was addressed.	Platform
894237	The issue where Global search could not be disabled on some pages was addressed.	Platform
1278031	The issue where users could not set up new alerts using DateTime was addressed.	Platform
1229785, 1244480, 1274324	The issue where manually created connections on Maps only showed when the Auto-Generated connection box was selected was addressed.	Platform
1264223, 1279159	The issue where scalability engines could be upgraded to the version installed on the main polling engine when upgrades for the main polling engine were available was addressed.	Platform
N/A	The issue where the name of sender was not specified for some out-of-the-box alerts was addressed.	Platform
1125893, 1220248, 1239230, 1244512, 1249564, 1251466, 1254246, 1258643, 1258669, 1260390, 1261995, 1262474, 1264367, 1265533	The partition management during the Database Maintenance was optimized.	Platform
N/A	The issue where installation/upgrade failed because of a locked file was addressed.	Platform
1241480	The issue where the send trap alert action stops working after the upgrade from 2020.2.6 was addressed.	Platform
1236663, 1236783, 1241870, 1242442, 1244793, 1249353, 1251317, 1273624	The issue when attempting to add accounts was addressed.	Platform
1207061	The installation error while running the centralized upgrade was addressed.	Platform
1249722	The issues with the "less than X objects meet the condition" condition in alerts were addressed.	Platform
1245612, 1248898	The issues with the Configuration Wizard launching automatically was addressed.	Platform
1244008	The issue where custom charts changed behavior was addressed.	Platform
1229115	The issue where AmsProxy logs stopped logging on log level change was addressed.	Platform
1237514, 1243831, 1245680, 1274269, 1289216	The issue where the node last boot was displayed using UTC was addressed. Last boot is displayed using the local time.	Platform
1154578	The issue with loading Subcategory when creating a ServiceNow incident was addressed.	Platform
826160, 864527, 873077	The issue where no error message was displayed when the upgrade failed was addressed.	Platform
1239689, 1279354	The issue where the Permission Checker fails on upgrade from 2020.2.6 for additional polling engines was addressed.	Platform
1228441	The issue where the category was not parsed correctly in All Nodes widgets was addressed.	Platform
1234160, 1254686	The issue where proportional widgets do not parse statuses was addressed.	Platform
1205283	The issue where Windows Agents generated high CPU usage was addressed.	Platform
1228673	The issue where the installation fails if there is another suspended MSI installation in the system was addressed.	Platform
1214950	The issue where latency between polling engines was incorrectly indicated on the main server was addressed.	Platform
1216266	The issue with time zones of SQL server and the main polling engine was addressed.	Platform
1187919, 1209102	The issue with Fortinet Fortigate 101E incorrectly polling IP addresses was addressed.	Platform
1202271, 1246753, 1256631, 1259934, 1263843, 1282054, 1289795	The issue where scheduled unmanaging issues caused false positive alerts was addressed.	Platform
1217121, 1291663	The issue where upgrade from 2020.2.6 fails in the Configuration Wizard when the bound HTTPS certificate is not available on the system anymore was addressed.	Platform
1194008	The issue where administrators could update the database with queries in the Add/Edit Report wizard was addressed.	Platform
1186572, 1288230	The issue where users could not save changed rows in Manage Entities was addressed.	Platform
1154256	The issue where users could not change the SNMPv3 credentials set for a node was addressed.	Platform
930171, 990401, 1048906, 1054670, 1095761, 1102507, 1208626	The issues with obsolete records in Cortex documents were addressed.	Platform
1163369	The issues with assigning a new dashboard as the default summary view were addressed.	Platform
1150632	The issue where the testing credentials for the execute external program alert action triggered the action instead of only validating the credentials was addressed.	Platform
1106632	The issues with using SQL/SWQL variables in the SMS alert action were addressed.	Platform
1128730	The issue where the Active Diagnostics test "Check Engines and OrionServers integrity" was case-sensitive was addressed.	Platform
1198603, 1204150, 1226617, 1228488, 1269783, 1278674, 1279332	The issue where the PerfStack real-time polling ignored account permissions was addressed.	Platform
1088944	The issue where volume charts behave differently for administrators and non-administrators was addressed.	Platform
318702, 874297, 932513, 1076268, 1200393	The issue where audit events for alert suppression showed time in UTC was addressed.	Platform
773793, 916997, 1092088	The issue where High Availability applications and components are not licensed was addressed.	Platform
631312, 807280, 817116, 1048102, 1051103, 1133802	The issues with latest baseline graphs were addressed.	Platform
N/A	Ping and Traceroute buttons for Engineer’s Toolset for the Web are now properly disabled if Engineer’s Toolset for Desktop and the Toolset Integration Tray are not installed on the server.	ETS Web
01073757, 01185940	ETS for Desktop tools now use the PC's default browser to launch links instead of Internet Explorer 11.	ETS Web
01239230, 01254246, 01264367, 01239230, 01258669, 01261995, 01260390, 01251466, 01248892, 01220248, 01258643, 01125893, 01265533, 01249564, 01262474	Database Maintenance no longer slows or fails due to high log entry retention.	LA
01264755, 01275830	Firmware vulnerability files can be downloaded and extracted without error when the URL and .zip file locations are valid.	NCM
01235110, 01241329, 01268731, 01270837, 01279594	Users can manage and edit NCM jobs from the Jobs List page without the process hanging or returning errors.	NCM
01279130, 01281943, 01287850, 01290108, 01291149, 01301934, 01302724, 01306120, 01309026	Configuration backups no longer fail if the archive folder is on a network share.	NCM
N/A	NCM 2023.2 includes security enhancements.	NCM
648291	The issue where Custom Interface Poller did not influence Node Status was addressed.	NPM
1175298, 1264916	The issue with an incorrect log level message for wireless tables in the Database Maintenance log was addressed.	NPM
1240079	The issue where special characters were escaped and thus not displayed correctly in the Node with Problems widget was addressed.	NPM
N/A	The issue where a setting to poll hardware health sensors with all statuses was ignored and new sensors were not polled was addressed.	NPM
N/A	All applicable regions for AWS are now available.	SAM
N/A	Zero-config is no longer failing with errors.	SAM
00990851, 00982470, 00993659	Database maintenance no longer fails or takes a long time to complete when a large amount of data is stored in IisBB_Site.	SAM
01248755	When collecting diagnostic information, Asset Inventory tables are now visible.	SAM
00858286	Active Alert page no longer displays the wrong name.	SAM
00998883, 01258501	The greater than and less than conditions now work correctly When creating an alert for API Poller Monitored Value.	SAM
01240750	HTTPS Monitor is now able to perform Search String searches on web page.	SAM
01279876, 01287977, 01288278, 01271813, 01273317, 01290754, 01293024, 01291507, 01231060, 01290325, 01290883, 01289617, 01295126, 01298316, 01301058, 01301006, 01278279, 01298525, 01303487, 01302920, 01298133, 01305835, 01308353, 01304992, 01309937, 01309270	The message stating SAM maintenance is overdue no longer appears.	SAM
N/A	The Windows installer is again functioning without issue during and after the upgrade on FIPS.	SCM
N/A	Asset Inventory information is again available in Orion diagnostics.	SCM
01273639, 01282025, 01297363	Issues when Active Directory Discovery fails were resolved.	UDT
00551644	Issue when Device Inventory shows non-existing extra connections with data from actual connections was resolved.	UDT
01254241	Issue when the Ethernet Ports Used Over Time widget stops rendering data after you upgrade from UDT 2020.2.6 was resolved.	UDT
00858005	Issue when UDT displays a vague error message while you shut down ports from UDT Port Details widget was resolved.	UDT
01152707	An issue causing the JobEngine to crash and resulting in out-of-memory exceptions in some cases is resolved.	VMAN
01209069	The issue with wrong MOS calculation for IP SLA VoIP UDP Jitter operations on Nexus devices was resolved.	VNQM
01023625, 01195930, 01222613	Issues with UDP Jitter and VoIP UDP Jitter operations not working on Cisco IOS XR and Cisco ASR9k devices were resolved.	VNQM
01239037	Issue when the upgrade from 2020.2.6 to 2022.4 fails was resolved.	VNQM
01235369	Issue with multiple SQL errors in logs has been resolved.	VNQM
01267994	Issue with VoIP CallManagers widget not rendering after installation was resolved.	VNQM

Installation or upgrade

Use the SolarWinds Installer to upgrade your entire SolarWinds Platform deployment (all SolarWinds Platform products and any scalability engines) to the current versions.

You must be on version 2020.2.1 or later to upgrade to the current version. If you are on 2020.2 or earlier, first upgrade to 2020.2.6 and then upgrade to the current version.

Before you upgrade from 2020.2.x

• Make sure the database user you use to connect to your SQL Server has the db create privilege. Without this privilege, the upgrade will not complete.

• The legacy syslog and traps functionality has been retired and replaced with new functionality called SolarWinds Log Viewer, which can be upgraded to Log Analyzer for additional capabilities. Current rules and history will automatically be migrated to the new logging functionality (SolarWinds Log Viewer or Log Analyzer). The functionality of SolarWinds Log Viewer and Log Analyzer has been improved to more closely match legacy functionality.

  If you built syslog and trap alerts using custom SQL queries, they will not function after upgrading to 2022.3 or later. SolarWinds recommends you rewrite the alerts using SWQL (Orion.OLM entities) or using the alerting functionality built into Log Viewer/Log Analyzer.

• Some upgrade situations from the Orion Platform to the SolarWinds Platform are not supported and the installer will stop the upgrade automatically.

  • If you have a SQL Server older than 2016.
  • If you have an Orion Platform product version 2020.2 or earlier.

Known issues

Last updated: November 1, 2023

Database login fails for Windows accounts after the upgrade

When you use Windows authentication to connect to the HCO database and the database SQL server, you can find Database: Login failed for user 'DOMAIN\MACHINENAME$' in the Website log. This can cause intermittent user logouts from the SolarWinds Web Console.

Resolution or workaround: Change the database account. See Database login failing for Windows account users after upgrading to 2023.1 and above.

Polling issues caused by the JobEngine being unable to submit a job

Polling issues caused by the JobEngine being unable to a submit job for some time. In SolarWinds.JobEngineService_v2023_2.log, you will find repeated “Unable to add worker process for” warnings.

Resolution or workaround:

1. On the main polling engine, back up the <installPath>\SWJobEngineSvc2.exe.config file.

2. Open the SWJobEngineSvc2.exe.config file, search for <jobSchedulerSettings_Full, and add the jobExecutionCount="10000000" parameter to jobSchedulerSettings_Full tag. The tag should start as follows:

   <jobSchedulerSettings_Full jobExecutionCount="10000000"

3. Restart the JobEngine service in SolarWinds Platform Service Manager.

4. Repeat the steps on all polling engines.

Custom SQL reports stop working after the upgrade to 2023.2

Resolution or workarounds:

• If you have issues with accessing the Flow Storage, the Log Analyzer Database, or any other database, see Custom SQL reports fail after the upgrade to 2023.2 (Error executing SQL: not able to access the database 'SolarWindsOrionLog', 'FlowStorage', or a custom database.

• If your report requires accessing the SolarWindsOrion database, see Custom SQL reports fail after the upgrade to 2023.2 (Error executing SQL: database 'SolarWindsOrion').

Changes to the SolarWinds Platform database

The implementation of time series widgets required changes to the SolarWinds Platform database. If you have custom reports or alerts that query the database, they could be affected by these changes.

Resolution or workaround: SolarWinds recommends using API calls instead of database queries to collect data for custom reports and alerts.

Cloud widgets not displayed for guest users

For guest users, errors are displayed instead of the Azure Cloud VM Management, Azure Cloud VM Details, and AWS Cloud Instance Management widgets.

Resolution or workaround: There is no workaround at the moment. SolarWinds is working on resolving this issue in a future version.

SAM templates show down/unknown status

After upgrading to 2022.3, SAM templates which utilize PowerShell (AppInsight, Custom Templates) show down/unknown status due to access denied errors.

Resolution or workaround:

1. Open the WebConsole and replace the path after Orion directory in the URL, as shown, and press Enter: Orion/admin/advancedconfiguration/global.aspx

2. In line: <add key="UseLegacyPowerShellImpersonation" value="false" /> change value to <add key="UseLegacyPowerShellImpersonation" value="true" />.

3. Click Save.

Wildcards in policy compliance rule search strings

When a policy compliance rule searches for a simple string (not a regular expression), the string cannot include the wildcard characters ? and *.

Resolution or workaround: To include wildcard characters, choose the Regular Expression (Regex) option as the string type.

Real-Time Change Detection does not send notifications

Real-Time Change Detection (RTCD) is configured in NCM. However, it does not send notifications when configs have been changed. This occurs because the default user no longer has the required permissions.

Resolution or workaround: To enable RTCD to send notifications, upgrade to NCM 2023.2.1 or later.

Incorrect size shown for VMware VM snapshots

Pages and reports that show snapshot sizes for VMware VMs can sometimes be incorrect.

"Triggered by Event" widget update delay

The "Triggered by Event" widget may in some cases not show the latest event that triggered the alert.

Monitoring a VMWare vCenter via ROP (Remote Orion Poller) shows unknown status

Unknown status can be incorrectly shown when monitoring a VMWare vCenter through a Remote Orion Poller.

Incorrect AppStack data for vCenters

AppStack data for a vCenter may in some cases be displayed incorrectly when the vCenter is deployed as a virtual machine under an ESXi host that is monitored by the same vCenter.

Account limitations may not work with VIM/VMAN groups

Account limitations may not work correctly in some cases with VIM/VMAN groups.

Custom charts show irrelevant host

Custom charts for VMAN clusters may sometimes show an irrelevant host in the chart legend.

Cluster Memory Utilization alerts sometimes show incorrect host

Incorrect hosts, even ones not in the relevant cluster, can sometimes be shown in Cluster Memory Utilization alerts.

Incorrect status shown for vCenter

If VMAN's polling process has failed for any reason, the last known status for a vCenter is shown in VMAN. This could result in a normal, green status being shown for a vCenter when it shouldn't.

End of life

Version	EoL announcement	EoE effective date	EoL effective date
2020.2.6	April 18, 2023: End-of-Life (EoL) announcement – Customers on SolarWinds Observability Self-Hosted version 2020.2.6 or earlier should begin transitioning to the latest version of SolarWinds Observability Self-Hosted.	May 18, 2023: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Observability Self-Hosted version 2020.2.6 or earlier will no longer actively be supported by SolarWinds.	May 18, 2024: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Observability Self-Hosted version 2020.2.6.
2020.2.5	January 18, 2023: End-of-Life (EoL) announcement – Customers on SolarWinds Observability Self-Hosted version 2020.2.5 or earlier should begin transitioning to the latest version of SolarWinds Observability Self-Hosted.	February 17, 2023: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Observability Self-Hosted version 2020.2.5 or earlier will no longer actively be supported by SolarWinds.	February 17, 2024: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Observability Self-Hosted version 2020.2.5.
2020.2.4	October 19, 2022: End-of-Life (EoL) announcement – Customers on SolarWinds Observability Self-Hosted version 2020.2.4 or earlier should begin transitioning to the latest version of SolarWinds Observability Self-Hosted.	November 18, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Observability Self-Hosted version 2020.2.4 or earlier will no longer actively be supported by SolarWinds.	November 18, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Observability Self-Hosted version 2020.2.4.
2020.2.1	October 19, 2022: End-of-Life (EoL) announcement – Customers on SolarWinds Observability Self-Hosted version 2020.2.1 or earlier should begin transitioning to the latest version of SolarWinds Observability Self-Hosted.	November 18, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Observability Self-Hosted version 2020.2.1 or earlier will no longer actively be supported by SolarWinds.	November 18, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Observability Self-Hosted version 2020.2.1.
2020.2	October 19, 2022: End-of-Life (EoL) announcement – Customers on SolarWinds Observability Self-Hosted version 2020.2 or earlier should begin transitioning to the latest version of SolarWinds Observability Self-Hosted.	November 18, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Observability Self-Hosted version 2020.2 or earlier will no longer actively be supported by SolarWinds.	November 18, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Observability Self-Hosted version 2020.2.
2019.4	July 27, 2022: End-of-Life (EoL) announcement – Customers on SolarWinds Observability Self-Hosted version 2019.4 or earlier should begin transitioning to the latest version of SolarWinds Observability Self-Hosted.	August 26, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Observability Self-Hosted version 2019.4 or earlier will no longer actively be supported by SolarWinds.	August 26, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Observability Self-Hosted version 2019.4.
2019.2	July 27, 2022: End-of-Life (EoL) announcement – Customers on SolarWinds Observability Self-Hosted version 2019.2 or earlier should begin transitioning to the latest version of SolarWinds Observability Self-Hosted.	August 26, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Observability Self-Hosted version 2019.2 or earlier will no longer actively be supported by SolarWinds.	August 26, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Observability Self-Hosted version 2019.2.

See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier SolarWinds Observability Self-Hosted versions, see SolarWinds Observability Self-Hosted release history.

End of support

This version of SolarWinds Observability Self-Hosted no longer supports the following platforms and features.

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.

Legal notices

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