If you encounter issues with those files, review requirements and note these details: You can create recordings for use as Transaction Checks in SolarWinds Pingdom, as described in Integrate WPM with SolarWinds Pingdom. Troubleshoot Web Transaction Recorder issues Enable FIPS mode for WPM on remote systems.Enable FIPS for SolarWinds Platform products.To learn more about this US Government standard, see: Check for the following entry: FIPS mode enabled.Navigate to the default log directory, C:\ProgramData\SolarWinds\Logs\SEUM\.CPU and memory usage may be impacted on remote systems, resulting in Down transactions.īefore troubleshooting WPM issues on a remote system, determine if FIPS mode is enabled by checking for a FIPS mode icon at the bottom of the Web Transaction Recorder window:Īnother way to check for FIPS mode is to examine logs. Some actions may fail, such as steps that involve certificate authentication. If your organization adheres to the Federal Information Processing Standard (FIPS) and FIPS mode is enabled on the SolarWinds Platform server, WPM may behave differently.įor example, recordings and transactions created in earlier versions of WPM may fail on remote systems where FIPS is now enabled. Look for related discussions in the SolarWinds online IT community, THWACK.Search for solutions in the SolarWinds Success Center, which also includes a WPM Troubleshooting Guide.Review WPM System Requirements and configuration details in the WPM Getting Started Guide.Monitor WPM logfiles with SolarWinds SAM.Collect diagnostic logs for WPM playback issues.Troubleshoot WPM Browser issues during playback.Troubleshoot Web Transaction Recorder issues.
This topic includes the following sections: Use this section to resolve common issues and learn about details to collect if you need to contact SolarWinds Support.
0 kommentar(er)
