Documentation forWeb Performance Monitor

WPM glossary

Action A single event within a step, such as clicking a mouse, entering text, or pressing the Enter key. Multiple actions can be included in a single step, and a group of steps makes a sequence.
Authentication binding When a client certificate is selected during a recorded sequence, the Web Transaction Recorder saves the name, issuer, and other identifying data about the certificate in the recording as an authentication binding. The certificate itself is not stored.
FIPS mode You can run WPM and other Orion Platform products in Federal Information Processing Standard (FIPS) mode to comply with computer security and interoperability standards used by non-military US government agencies and contractors.
Managed transaction A transaction that is assigned to a location and actively reporting statistics to the Orion Web Console. Managed and unmanaged transactions count against your WPM license.
Orion server

The primary server used by the Orion Web Console and Orion Platform products.

Orion Web Console The web interface where you interact with Orion Platform products. In addition to displaying WPM data and reviewing events, you can use the Orion Web Console to deploy the Web Transaction Recorder and the SolarWinds WPM Player Playback service to remote systems, schedule transactions to play at regular intervals, or configure thresholds for alerts.

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

Not using Pingdom yet? Click here to start a free trial.

Recording A series of navigational steps and actions that are captured as a recording. After you assign a recording to a transaction location for playback, it becomes a transaction monitor. Recordings do not count against your license, but managed and unmanaged transactions do.
SEUM-User account

When the WPM Player Playback service plays transactions at scheduled intervals, it uses a different WPM worker process to perform each step in a transaction. Each worker process requires a SEUM-User account that provides permission to perform a transaction step.

By default, the Orion server includes 2 SEUM-User accounts. When you deploy WPM Players to remote systems, 7 accounts are included. You can adjust accounts to make environmental changes, such as adding proxy settings or adjusting permissions. You can also add accounts if necessary, with a recommended maximum of 12. The limit of accounts on a player depends on the power of the host system (CPU, RAM, and so on).

Synthetic End User Monitor (SEUM) was the original product name for WPM.

SolarWinds WPM Playback Player service

Also called "the WPM Player," this service is installed on the Orion server, Additional Polling Engines (if applicable), and any remote systems where it was deployed.

  • Function: Plays recorded transactions at scheduled intervals. Also manages WPM worker processes that play individual steps in each transaction.
  • File name: Solarwinds.SEUM.Agent.Service.exe
  • Default location: C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player

If your environment includes SolarWinds SAM, you can use the SolarWinds Web Performance Monitor (WPM).apm template to monitor this service, as well as the SolarWinds WPM Playback Proxy service, described next.

SolarWinds WPM Playback Proxy service

This service is installed on the Orion server and Additional Polling Engines, if applicable.

  • Function: Supports communication between active instances of the SolarWinds WPM Playback Player service that play recorded transactions at scheduled intervals.
  • File name: Solarwinds.SEUM.AgentProxy.Service.exe
  • Default location: C:\Program Files (x86)\SolarWinds\Orion\SEUM.
Transaction A transaction is a recorded sequence of web browser steps assigned to a specific location.
Transaction location After creating a transaction, designate where the transaction plays, which can be the Orion server, a cloud instance, or a remote system where a WPM Player was deployed. Transaction locations are sometimes referred to as "player locations" or "playback locations."
Transaction step A step is a collection of actions within a recorded transaction. For example, the actions required to navigate to a specific URL make up one transaction step. Each step uses a different WPM Worker process that provides permissions needed to complete the step.
Unmanaged Transaction

An unmanaged transaction is a WPM transaction currently assigned to a specific location, but purposely set as inactive so it does not report statistics to the Orion Web Console. See Stop and start WPM transaction monitoring.

When a transaction is unmanaged, historical data is retained and the transaction counts against your WPM license.

Web Transaction Recorder

A program, accessible from the Windows Start menu, that captures web browser steps as you perform them to mimic typical steps performed by end users, such as mouse clicks, text input, and authentication.

After recording a transaction, you can schedule it to run at regular intervals on systems that host the SolarWinds WPM Player Playback service, also known as WPM Players.

Webview The area of a web page that can be captured in a recording, and then later tracked during playback. See Track click coordinates in the Web Transaction Recorder with X, Y Capture Mode.
WPM Browser The browser used by the WPM Player to play recorded transactions, as stored on remote systems in the following default directory:
C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\ChromiumProbe\WPM Browser\WPM Browser.exe.config
WPM Player

A remote system that hosts the SolarWinds WPM Playback Player service that runs recorded transaction at scheduled intervals. For details, see Deploy WPM Players to remote systems.

You may also see WPM Players referred to as "transaction locations" or "playback locations" because they're created when a recorded transaction is assigned to a specific location and played at scheduled intervals.

WPM worker process

The SolarWinds WPM Playback Player service uses WPM worker processes to play back transactions, collect statistics, and return results to the Orion Platform. Each WPM worker process requires its own SEUM-User account because different processes handle different transactions at different times, and may require specific permissions.