Documentation forWeb Performance Monitor

Manage transaction locations in WPM

Transaction locations (also called "playback locations") are remote systems in your environment where WPM Players are deployed. You can also use a WPM Player deployed to an Additional Polling Engine as a transaction location.

Although a WPM Player is added to the SolarWinds Platform when you install the primary WPM application, SolarWinds recommends against using the SolarWinds Platform server as the primary location to play transactions. For details, see Deploy WPM Players to remote systems.

Per the Scalability Engine Guidelines for SolarWinds Products, SolarWinds recommends limiting the number of monitored transactions assigned to a WPM Player to 12 or less. However, note that many factors can impact the load on transaction locations that host WPM Players, including:

  • The complexity of assigned transactions.
  • The length of playback for each transaction.
  • The length of intervals between each transaction playback.
  • The processor speed and RAM available on the system hosting the WPM Player.
  • The number of WPM Player service accounts or domain accounts involved in playback. See Manage WPM Player service accounts.

You can check the WPM Player load on a remote system in the Player Load Percentage widget, as described in Display transaction locations in WPM.

Use the Manage Transaction Locations page to add, edit, and delete transaction locations in the SolarWinds Platform Web Console, as described in: