SolarWinds Observability Self-Hosted 2022.4.1 release notes
Release date: December 14, 2022
These release notes describe fixed issues in SolarWinds Observability Self-Hosted 2022.4.1. They also provide information about upgrades and describe workarounds for known issues.
SolarWinds Observability Self-Hosted 2022.4.1 runs on SolarWinds Platform 2022.4.1.
- For information about platform-related updates and changes included with this release, see SolarWinds Platform 2022.4.1 Release Notes.
- For information about requirements, see SolarWinds Platform 2022.4 system requirements.
New features and improvements
SolarWinds Observability Self-Hosted 2022.4.1 is a service release and provides stability fixes compared to previous releases of SolarWinds Observability Self-Hosted. New features and improvements from SolarWinds Observability Self-Hosted 2022.4 are included.
SolarWinds Observability Self-Hosted 2022.4.1 runs on SolarWinds Platform 2022.4.1. See also the SolarWinds Platform 2022.4.1 Release Notes.
New customer installation
For information about installing SolarWinds Observability Self-Hosted, 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 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 2022.4.1, 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, 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.
- Make sure all your legacy reports are migrated. You won't be able to access legacy reports and related tools anymore.
-
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. See LA 2022.3 release notes for details.
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.
- If you customized your website directory, please note that during the upgrade, the website directory will be moved to the location where the application is installed. There are no options in the installer to customize the website location.
- After upgrading to SolarWinds Observability Self-Hosted from an Orion Platform 2020.2.6 installation, you will need to update your MIB database.
- 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 older than 2020.2.
How to 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 Orion Platform 2020.2.1 or later to upgrade to SolarWinds Observability Self-Hosted 2022.4.1. If you are on Orion Platform 2019.4 or earlier, first upgrade to Orion Platform 2020.2.6 and then upgrade to SolarWinds Observability Self-Hosted 2022.4.1.
Fixed issues in SolarWinds Observability Self-Hosted 2022.4.1
SolarWinds Observability Self-Hosted 2022.4 fixes the following issues:
CASE NUMBER | DESCRIPTION |
---|---|
1227273 |
The SWIS memory leak on installations in foreign languages was addressed. |
1205138 | The issue where the Active Alerts page was empty even though users could see alerts in the message center or on the Events page. |
1207212, 1215487, 1216432, 1222317, 1222853, 1223295, 1225682 | The issue where SWIS was crashing after startup after the upgrade to 2022.4 was addressed. |
01190503, 01205944, 01214915 | Issues when CPU spikes occur when you upload multiple CDR and CMR files simultaneously were fixed. |
01110702 | Parent node no longer shows wrong application monitor status. |
00927195 | Cell values no longer show date instead of number value when exporting custom charts. |
01012377 | Adding new Windows group account to the server no longer returns an error. |
01016374, 00691802 | When applying an application template to multiple servers, the template no longer gets applied multiple times. |
00520035 | The graphical report for log parser now shows the correct information. |
01060801 | The All Applications widget, in the Applications Summary page, is no longer showing duplicates for AppInsight for SQL monitors. |
SolarWinds Observability Self-Hosted 2022.4.1 includes all of the fixed issues in SolarWinds Platform 2022.4.1. See the SolarWinds Platform 2022.4.1 release notes.
CVEs
SolarWinds would like to thank our Security Researchers below for reporting on the issue in a responsible manner and working with our security, product, and engineering teams to fix the vulnerability.
SolarWinds CVEs
CVE-ID | Vulnerability Title | Description | Severity | Credit |
---|---|---|---|---|
CVE-2022-47512 | Sensitive Data Disclosure Vulnerability | Sensitive information was stored in plain text in a file. The file is accessible by a local account who specifically has been given access to the application server. This affects SolarWinds Observability Self-Hosted / SolarWinds Platform 2022.4. No other versions are affected. | 6.0 Medium |
Thwack MVPs |
Notes - BugCrowd
SolarWinds would like to additionally thank our Bugcrowd community for their continued help in testing our products and keeping them secure.
Known issue
Changes to the SolarWinds Platform database | |
---|---|
Issue | 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. |
Legal notices
© 2022 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.