Documentation forWeb Performance Monitor

How WPM works

SolarWinds Web Performance Monitor (WPM) is an advanced tool for automating web transactions and measuring the response time of web servers and web applications. WPM constantly replays recorded transactions (every 5 minutes, by default) to:

  • Check if web servers or applications are up, down, or experiencing high loads.
  • Continuously monitor the end-user experience for each step of a web transaction track duration, dependencies, alerts, and more.
  • Monitor any web application, whether internal (behind the firewall), external (customer-facing), or cloud-based.

With WPM, you can record a variety of transactions and then play them back at scheduled intervals, from various locations, to simulate end user experiences with web servers and Software as a Service (SaaS) applications. By tracking the performance of the same transactions running repeatedly over time, you can use WPM to find and fix web performance issues in both internal and customer-facing applications before users are affected. Quickly find the root cause for performance issues by examining DNS lookup data, connection time, send time, time to first byte, or content download time.

For example, if WPM monitors a transaction step that usually takes 2 seconds to complete and the duration suddenly jump to 10 seconds, WPM can notify you so you can investigate the situation. With synthetic transaction monitoring, you can proactively identify if slow website services are impacting the user experience.

The following figure shows a high-level overview of how WPM components interact:

You can deploy WPM Players to remote systems to sample the typical experiences of end users in various locations around the world. For example, if a large part of your customer base is in western Europe, you can deploy a WPM Player to a workstation in Germany and schedule transactions to run several times per day to monitor the performance of a website hosted in Boston.

WPM uses the following components to achieve comprehensive web performance monitoring:

  • The Orion Server is the primary server that hosts Orion Platform products, including WPM. This server hosts the Orion Web Console where users interact with products and view gathered information. It also includes a Web Transaction Recorder and the WPM Player service. The Orion server monitors synthetic transactions that run continually, displays statistics in the Orion Web Console, and triggers alerts when it detects deviations in playback times.
  • The Web Transaction Recorder is a separate tool you can open from your desktop to capture web browser steps as you perform them, simulating the typical steps taken by end users to create synthetic transactions. This tool is also called the WPM Recorder.
  • Assign a recording to one or more playback locations to create transactions that play at regular intervals; the default is 5 minutes. The original recording is a raw file, but the transactions are an active monitors that perform web actions based on the steps in the file to gauge performance. You can set timing thresholds to trigger alerts if transactions exceed expected run times.
  • The WPM Player is a Windows service that deploys, manages, and communicates with WPM worker processes to simulate end user experiences by playing back transactions at scheduled intervals. The WPM Player service reports statistics about transactions to the Orion server.
  • The WPM Player service uses WPM worker processes to:
    • Log into the local system that hosts the WPM Player service,
    • Play back the transaction steps of a recording, and
    • Collect statistics and screenshots during playback.
  • WPM Worker processes rely on SEUM-User accounts included with WPM for permissions.

    SEUM-Users must be members of the local Administrator group on the system hosting the WPM Player that will use them.

  • The Orion Web Console displays WPM statistics so you can interact with them. You can display details about transactions, including transaction step durations and screenshots, in various WPM views and widgets.

Here's an overview of what happens after you assign recordings to remote systems that host the WPM Player service in various locations:

  1. The Orion server sends requests to remote systems to play transactions at scheduled intervals.
  2. The WPM Player service runs transactions repeatedly while collecting statistics for each step, as well as entire transactions.
  3. The Orion server requests playback results from the WPM Player service.
  4. The WPM Player service submits playback results to the Orion server.
  5. In the Orion Web Console, WPM views and widgets display updated statistics that indicate how transactions perform over time.
  6. WPM alerts are triggered based on gathered data and configured thresholds.

Use WPM with SolarWinds Pingdom

Starting in WPM 2020.2, you can save recordings as Transaction Checks that can be used in SolarWinds Pingdom, a subscription-based, SaaS application that provides synthetic monitoring and Real User Monitoring (RUM). The RUM capabilities in Pingdom provide you with insights into the behaviors and experiences of actual end users.

To learn more:

Not using Pingdom yet? Click here to start your 14-day free trial.