• Two different tests provisioned from the same script
  • Customer copy of a benchmark script
  • Synthetic Monitoring Backbone



Many times accounts will have two copies of the same test. most popular reason is when you are part of a benchmark. Most accounts report on the benchmark they are in. Having your own internal copy of that test allows you to alert on the test and collect SCoE (Screen Capture on Error) when failures occur.


Two tests provisioned from the same script will always have a different response time because they are two different tests. Even if the tests are identical, always hitting the same back-end servers and running from the same nodes at the same frequency, the results can still vary from minute to minute and there is no way to ensure they will run at the same minute. In other words, results captured at 12:05 could be different from those at 12:10.

For the closest response time possible, we recommend that you make sure the nodes and frequency of your test are identical to that of the Benchmark test.

Root Cause

The Benchmark test is publishing the data collected based on methodology. All the companies included have the data collected from the same nodes running at the same frequency. This provides an accurate comparison of them.

Any data point is an accurate measure of that moment in time. The more data points you have, the fuller and more comprehensive the average becomes.

  • No labels