Transaction Threshold Metrics

Note: The Service-Level Agreement feature is an alternative to setting up a Transaction Threshold using the Jenkins Plugin. Please see the Service-Level Agreement help article for more details.

Average Response Time - The average amount of time spent establishing the connection, sending the request, and receiving and processing the response for objects in this transaction. Response time excludes any time spent waiting for a connection to be available from the internal connection pool

90th Percentile - CloudTest calculates a 1-tailed confidence interval, meaning that the outliers removed to obtain the 90th percentile are the slow response times, but not the really fast ones.

Min Response Time - The smallest value of the transaction’s duration for all actions in it and any containers it contains that did complete a request.

Max Response Time - The largest value of the transaction’s duration for all actions in this container and containers it contains that did complete a request.

Total Bytes Sent - The sum of all of the Total Bytes Sent values for all actions in this transaction and containers it contains that did complete a request.

Errors Per Transaction - Non-zero if any items in this transaction or the containers it contains had errors. "Having errors," means an item that completed successfully but generated events of level "Error" during play, as well as items that failed during play.

Minimum Transaction Count – The smallest sum of the transactions that completed a request.

  • Once the Threshold is selected, enter a value. For example, 234 (expressed in milliseconds) for Max Response Time below.
  • If more than one Transaction will be tracked, click Add to place additional Transaction Threshold forms into the Jenkins job.
  • Click Save to save and exit the Jenkins job after making changes, or click Apply to save and continue editing the job configuration.