Documentation forWeb Performance Monitor

Create WPM transaction monitors

After creating a WPM recording, you can use the Add Transaction wizard to create a WPM transaction monitor by assigning the recording to a WPM Player hosted on a system at a specific location, known as a "transaction location" or "playback location." You can also assign a single recording to different transaction locations to create multiple transaction monitors that run the same steps.

Each WPM transaction monitor requires:

  • A recording.
  • An assigned transaction location.

Create a transaction monitor with the Add Transaction wizard

To create a transaction monitor, select a recording and assign it to a playback location:

  1. Click Settings > All Settings > WPM Settings.
  2. Click Add a Transaction Monitor to open the Add Transaction wizard.

    You can also open the wizard from the Discovery Central page.

  3. Select a recording and click Next.

    To import a recording, click Import, browse to the file, and click Import.

  4. Select the location where you want to play the recording, and then click Next.

    To add a location, see Add transaction locations in WPM.

After you select a recording and assign it to a location, define the properties for the transaction monitor.

  1. Enter a Description.
  2. Select a Playback interval to specify how frequently you want to play the transaction.
  3. Select Set thresholds in WPM for each step in the transaction.
  4. (Optional) To use a Proxy URL, click Advanced, and enter the proxy server address in the Proxy URL field. A proxy server acts as an intermediary that passes requests and responses to the client application, as described in Configure proxies for WPM transaction locations and transactions.
  5. To enable screen captures, click Advanced, and enable that option.
  6. Click Save Monitor.

To improve transaction troubleshooting, set dependencies on transaction steps as well as transactions, providing an increased level of granularity to isolate dependencies at the level of single browser actions. See Configure WPM transaction dependencies.