Threshold Settings dialog box
To identify significant differences in performance, you can define unique thresholds to track differentials between measurements being compared. If a differential exceeds a defined threshold, that value appears in a predetermined color, identifying it as a minor difference, or major difference.
| To access
|
On the <report name> PAL Report, click  Thresholds.
|
| Important information
|
- The term transaction applies to any activity measured by testing and production systems. This includes VuGen script transactions, RUM transactions and actions, and URLs measured by other production systems.
- The threshold definition and color settings are applied on a global level and hold true across all views in the report.
|
User interface elements are described below (unlabeled elements are shown in angle brackets):
|
UI Elements
|
Description
|
| Measurement Type
|
The type of measurement.
|
| Minor Difference
|
Enter a threshold value for indicating a minor difference between the production and test data.
|
| Major Difference
|
Enter a threshold value for indicating a major difference between the production and test data.
|
| <color settings>
|
Enables you to select in which color the
measurement appears in the report. Click the colored square in the column to select a different color for the measurement.
|
| Response Time
|
Measures the average response time transactions take to complete (in seconds).
|
| Hits
|
Measures the total number of transaction hits over the entire test run.
|
| Hits Distribution
|
The percentage of transaction hits occurrence from the total amount of all transaction hits. |
| Users
|
Counts the number of users that performed a specific transaction. |
| Users Distribution
|
The percentage of transaction users from the total amount of users in all transactions. |
| Time In System (Hits X Response time)
|
Total time a specific transaction was running in the system. Calculated by multiplying the average transaction response time by the number of hits. |
| Transactions per Second (TPS)
|
The number of times a transaction was executed in a second. Calculated by dividing the number of hits by the duration of the data set. |
| SiteScope Monitors (SiS)
|
The metrics monitored by SiteScope. |
Back to top
