Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Web Performance Monitor (WPM) > WPM Documentation > Web Performance Monitor Administrator Guide > Manage WPM transactions

Manage WPM transactions

Table of contents
No headers

Updated: September 18, 2018

After using the WPM Recorder to capture a series of steps that simulate typical actions taken by end users of a web application, you can assign the recording to a player location to create a transaction.

Player locations are also called transaction locations in WPM. Both terms refer to recordings assigned to specific locations.

Transactions are more than just recordings matched up with locations. The original recording is a raw file but the transaction is an active monitor that performs web actions based on the steps in the file to gauge performance. You can schedule transactions to play at regular intervals and set timing thresholds so WPM triggers alerts in the Orion Web Console if transactions exceed their expected run time.

To learn more, see:

Last modified