Release date: August 25, 2020
Updated September 17, 2020
These release notes describe improvements, upgrade tips, fixed issues, and known issues in SolarWinds Web Performance Monitor 2020.2.1.
US government organizations can now enable Federal Information Processing Standard (FIPS) mode on remote systems that host a Web Transaction Recorder and the WPM Player service. Note that WPM behaves differently in FIPS mode. Some features, such as saving recordings as Transaction Checks for Pingdom, are not supported. CPU and memory usage may also be impacted on remote systems.
To learn more, see:
In addition, WPM User Role options allow more flexibility when providing other members of your organization with permission to:
- Access various WPM views in the Orion Web Console, such as the WPM Summary view.
- Manage recordings, transaction monitors, and player locations.
Note the following details about this service release:
- System requirements have not changed. Use the WPM 2020.2 System Requirements.
- WPM 2020.2.1 consumes Orion Platform 2020.2.1, which includes Orion Platform hotfixes released on or before August 25, 2020.
- For release notes for earlier WPM versions, see Previous versions.
- Support for Microsoft Windows Server 2012 R2 remains available so WPM 2.2.3 customers can upgrade to the latest version of WPM. SQL Server 2012 is also supported.
Now that the Web Transaction Recorder (previously called the "new WPM Recorder") is a mature feature, we recommend using it to create all recordings, instead of the Deprecated WPM Recorder. Future WPM releases may not support the ability to edit recordings or play transactions that originate in the Deprecated WPM Recorder.
To install WPM, review system requirements and use the SolarWinds Orion Installer, which you can download from the SolarWinds Customer Portal. See the Orion Platform Products Installation and Upgrade Guide to learn how to prepare your environment and use the Orion Installer.
After installing WPM on the Orion server, you can deploy Web Transaction Recorders and WPM Players to remote systems to get an accurate sampling of your websites and services from the viewpoint of your end users. See the WPM Getting Started Guide for details.
To prepare for the upgrade:
- Read these Release Notes.
- Confirm that all servers comply with WPM 2020.2 System Requirements.
- (Optional) Back up any custom code, such as modified SolarWinds .css files or added .js files. Click here for tips.
In addition, note the following details:
- To migrate WPM as part of an upgrade, see the Orion Platform Migration Guide. Be sure to update SEUM agents to point to new EngineIDs, as described here.
- If currently using WPM 2.2.2 or earlier, upgrade to WPM 2.2.3 first, and then upgrade from WPM 2.2.3 to the latest version.
- Transactions based on recordings created in WPM 2020.2 and earlier may behave differently if FIPS mode is enabled. Steps that aren't FIPS-compliant (for example, steps that require NTLM authentication) may cause transactions to fail or return false-positive results.
SolarWinds recommends enabling FIPS on the Orion server as part of a fresh deployment instead of during an upgrade. See Enable FIPS for Orion Platform products.
How to upgrade
- Use the SolarWinds Orion Installer to upgrade your entire Orion deployment, including all Orion Platform products and any scalability engines.
Click Settings > My Orion Deployment to upgrade from within the Orion Web Console instead.
- Update WPM Recorders and WPM Players on remote systems. See the WPM Getting Started Guide.
- If you migrated WPM during the upgrade, update EngineIDs for SEUM agents, as described here.
|Language settings for Turkish locales were updated to resolve intermittent issues with status reporting for encrypted recordings.|
|Code was updated so transaction widgets refresh properly when switching between a main WPM view (such the Transactions Summary view) and a NOC view.|
|The TCP Waterfall Chart displays data for a transaction both cumulatively and sequentially, across all steps.|
|To support applications that generate dynamic URLs for each SSO login attempt, authentication credentials are no longer bound to a specific URL when creating recordings. Previously, customers reported "Playback Failed: Unable to navigate to the page. Reason: Unauthorized" messages if URLs didn't match.|
|Recordings played back on the WPM Player have a smaller screen size than when created in the Deprecated WPM Recorder.||Recordings created in WPM 2.2.3 and earlier don’t store original screen sizes. For a workaround, click here.|
|Transactions based on recordings created in the Deprecated WPM Recorder that involve certificates may cause a WPM Player to crash on Windows Server 2016 Standard, Windows Server 2019 Standard, or Windows 10 v. 1607 or later||Click here for a workaround that adds the monitored page as a trusted site.|
|The Deprecated WPM Recorder doesn't count duration time on web pages with automated redirects.||If a recording navigates to a web page that includes a redirect to another web page, the time spent navigating to the first web page is not included in the overall duration time. Click here for a workaround.|
|Web Transaction Recorder may stop responding if invalid credentials are provided.||If you enter invalid credentials for a recording to which multiple authentications were applied, the Web Transaction Recorder may switch to an unusable state that displays a "Digest" graphic.|
|If using Image Match with Basic Authentication, dynamic iFrame pages appear blank during action-by-action playback.||In the Web Transaction Recorder, if you navigate to a dynamic iFrames page while using Image Match with Basic Authentication and click the Play action-by-action tool, the page that WPM tries to authenticate does not display any content.|
|Some WPM pages and widgets aren't compatible with Internet Explorer (IE) 11.||Warning messages may appear when using IE 11 with features introduced in WPM 2020.2 or later. Use Chrome, Firefox, or Microsoft Edge for the optimum WPM experience in the Orion Web Console.|
|Invalid time calculated for steps with implicit navigation in the Web Transaction Recorder.||Recordings that include implicit navigation (for example, navigate to a page and download images with delays of up to 5 seconds each), the time calculated for the implicit steps may not be accurate.|
|Page titles do not appear in the Recorded Steps pane of the Web Transaction Recorder when using links to navigate to different tabs on the same page.||This occurs if WPM cannot access the window.opener property of the Windows interface, so the title of the web page is not captured in the recording. As a workaround, enter a URL to switch to a new tab on the same page, instead of clicking a link.|
|WPM Player service restarts and reconnects after agent communication exceptions||If the WPM Player service is overloaded, fatal exceptions can cause the service to restart as it dispositions WPM worker processes. Click here for a workaround.|
|After exporting recording with Image Match steps from the Deprecated WPM Recorder, error occurs when you try to save the file.||To work around this issue, save the file before you export it.|
See the End of Life Policy to learn more about life cycles for SolarWinds products.
|EoL Announcements||EoE Effective Dates||EoL Effective Dates|
August 25, 2020
End-of-Life (EoL) announcement – Customers on WPM 2.2.3 and earlier should begin transitioning to the latest version of WPM.
November 25, 2020
End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WPM 2.2.3 and earlier will no longer be actively supported by SolarWinds.
November 25, 2021
EoL – SolarWinds will no longer provide technical support for WPM 2.2.3 and earlier.
© 2020 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.