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. If you see the response time of an action varies between 1—4 seconds, simply add a 5-second wait after the step to accommodate that variation.

Although wait times won’t be 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 for text validation or Image Match but errors occur because 1—4 seconds is not enough time, you can extend the request timeout value for an entire Web Transaction Recorder or WPM Player service.

  1. Log into the host system.
  2. In a file editor such as Notepad, 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 Player service C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\SolarWinds.SEUM.Agent.Service.exe.config
  3. Add the following lines to the file:

    <fips>

    <requestTimeout>300</requestTimeout>

    </fips>

  4. Save your changes.
  5. Restart the Web Transaction Recorder and/or WPM Player service.