Specifications

Tracking Timed-Out Transactions
reported time for a Notes transaction exceeds 10 minutes, Application
Response counts it as a timed-out transaction and does not include its
response time data in average response time calculations. To report on the
rate of timed-out transactions, you can run a Trend report on selected
response paths for the Transaction Timeouts variable.
Application Response will track timed-out transactions when you set upper
limits (using the less than sign < ) for any of the following time-based
constraints: ClientTime, ElapsedTime, NetworkTime, N1NetworkTime,
N2NetworkTime, ReportedTime, ServerTime, ThinkTime. You can define these
limits at the application level or the transaction level, and you can define
multiple limits for each application and transaction. For examples, refer to
Transaction-Specific Elapsed and Reported Time.
Defining Lower Time Limits
If you define a lower time limit for an application or transaction (using the
greater than sign > ) and a transaction falls below the limit, Application
Response ignores the transaction and discards its response time data. In this
way, the spurious transactions do not skew the average response time to
produce misleading results. However, Application Response does not track
these discarded transactions as timed-out transactions, and you cannot report
on them.
For example, suppose that you add the following ElapsedTime constraint to the
default constraints for the Lotus Notes application.
[
BytesSent > 0
ServerName != "No-Server"
ElapsedTime > 1000
]
The ElapsedTime constraint indicates that Application Response is to track
response time for transactions whose total elapsed time (client time + network
time + server time + think time) is greater than one second. If elapsed time
for a Notes transaction is less than one second, Application Response is to
discard the transaction and not include its response time data in average
response time calculations. You cannot report on transactions that do not
reach a lower limit.
Observing Timed-Out Transactions in BT Studio
When you test application rules in BT Studio, the Transactions tab of the
results pane lists all transactions (from the open event log file) that match the
defined rules. If a transaction's response time will not be reported by
Application Response due a constraint or time limit, the Transactions tab
216 BTStudio Administration Guide