Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Web Performance Monitor (WPM) > WPM Documentation > Web Performance Monitor Administrator Guide > Transactions > Creating transactions > Thresholds


The default threshold timing values for a 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
  • Critical: Four times the initial step timing

The Warning and Critical thresholds are used to trigger alerts. The Typical Value is plotted as a benchmark on resource charts that you can use to compare with actual timings.

You can change the default values if required.

  1. From the Home tab, navigate to Home.
  2. Click a transaction in the All Transactions group.
  3. Click Edit on the Management line.


    The Edit Transaction Monitor page is displayed, where you can edit the thresholds.

Adjusting thresholds for network latency

There may be a need to set different timing thresholds for transactions that are played back from drastically different geographical locations.

For example: If you use a recording to create a transaction that will play back on a 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, you will need to raise the timing thresholds to account for the added network latency.

Thresholds are not required to create a transaction.

Last modified