Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

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

Set WPM thresholds

Table of contents
No headers

Updated: September 18, 2018

The default threshold timing values for a WPM transaction are based on the step timings measured when a recording was saved:

  • Typical Value: the initial step timing
  • Warning: Twice the initial step timing (triggers alerts)
  • Critical: Four times the initial step timing (triggers alerts)

The Typical Value is plotted as a benchmark for comparison with actual timings, as shown in the following example:


You can adjust timing thresholds for transactions played back from drastically different geographical locations. For example, if you run a transaction on a WPM Player that is 100 miles away from the original recording location, the default threshold timings are probably sensible. However, if the player is 2,000 miles away, consider raising timing thresholds to account for the added network latency.

To configure thresholds for WPM transactions:

  1. Navigate to My Dashboards > Transactions Summary.
  2. Click a transaction in the All Transactions widget.
  3. Click Edit on the Management line.


  4. On the Edit Transaction Monitor page, edit threshold values as necessary and click Save.

Thresholds are not required to create a transaction.

Last modified