Specifications

Tracking Timed-Out Transactions
BT Language Reference 215
Operator Description Valid Values Example
>= Greater than or
equal to
Integer BytesSent >= 0
!= Not equal to (for
use with
ServerName only)
String enclosed in quotes ServerName !=
"No- Server"
= Equal to Integer BytesSent = 0
When Application Response observes a transaction that exceeds an upper time
limit (such as [ ElapsedTime < 900000 ]), it adds that transaction to the
Transaction Timeouts counter and excludes the response data from other
eHealth reports.
When Application Response observes a transaction that falls below a lower
time limit (such as [ ReportedTime > 1000 ]) or that does not meet some
other limit (such as [ BytesSent >= 0 ]), it discards the transactions' data. The
transaction is not included in the Transaction Timeouts counter, and its data is
not included in any eHealth reports.
Value
For value, specify the desired limit or constraint. Enclose string values in
double quotes (").
Tracking Timed-Out Transactions
When you define upper time limits for transactions, Application Response can
track the number of transactions that time-out (exceed the upper limit), so
that you can report on them. This information can help you to understand how
many transactions take too long. And by setting upper time limits, you ensure
that these too-long transactions do not skew average response times.
For example, suppose that you add the following ReportedTime constraint to
the default constraints for the Lotus Notes application.
[
BytesSent > 0
ServerName != "No-Server"
ReportedTime < 600000
]
The ReportedTime constraint indicates that Application Response is to track
response time for transactions whose total reported time (client time +
network time + server time) is less than 10 minutes (600,000 milliseconds). If