Documentation forWeb Performance Monitor

Add wait time to WPM recordings

Variations in response times and false alerts about failed transactions can make it difficult to fine-tune your web application performance monitoring. Responses can be slowed due to Internet connection issues, OS performance issues, applications that are not yet optimized, or pages with complex elements that need extra time to load.

If you encounter false alarms due to these types of variances, consider adding some ‘waits’ (that is, artificial pauses) to recordings. For example, if an action has a response time of 1—4 seconds, add a 5-second wait time after the step to accommodate that variation.

Although wait times aren't included in the recorded time for transactions, they can help to absorb the changes in the response times.

To add wait time to a step or action in the Web Transaction Recorder:

  1. Click Add Wait Time .
  2. Edit the time as needed, and click Add.

Configure WinHTTP request timeouts

If you add wait time to a text validation or Image Match step but it still fails, try extending the request timeout value for either:

  • The Web Transaction Recorder, or
  • The WPM Browser service that supports transaction playback on remote systems.

To configure request timeouts:

  1. Log into the host system.
  2. In a text editor, open the config file where you want to adjust settings.
    • Web Transaction Recorder: C:\Program Files (x86)\SolarWinds\Orion\SEUM\Recorder\WPM Recorder.exe.config
    • WPM Browser: C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\ChromiumProbe\WPM Browser\WPM Browser.exe.config

      Changes made to the WPM Browser config file apply to all transactions played on the host system.

  3. Add the following lines to the file:

    <fips>
    <requestTimeout>300</requestTimeout>
    </fips>

  4. Save your changes.
  5. Use the Orion Service Manager to restart the Web Transaction Recorder or WPM Browser service, depending on which item was updated.