Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Web Performance Monitor (WPM) > 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