Specifications

How Transaction Limits Work
# ServerName != "No-Server"
]
When an application rule set includes any transaction limit or constraint,
Application Response ignores the default constraints and applies the defined
limit or constraint when monitoring transactions. If the application does not
have associated server activity, the response path name on reports shows
"No-Server" instead of a server name, similar to the following:
Client Module An application
name name path
yellow- Outlook- Read-No-Server- AP
Application No server
name activity
Using Transaction Time Limits
Application Response provides several ways to set transaction time limits:

Default elapsed and reported time

Application-specific elapsed and reported time

Transaction-specific elapsed and reported time
Elapsed time refers to the amount of time that elapses during the entire
transaction, from the moment the transaction begins to the moment it ends.
This includes client time, network time, server time, and client think time (also
called idle time). Reported time includes client time, network time, and server
time, but it does not include client think time. Application Response reports
show reported time.
An application-specific limit overrides a default limit, and a transaction-specific
limit overrides an application-specific limit. In addition to limits on elapsed and
reported time, you can also set other types of transaction limits and
constraints.
Default Elapsed and Reported Time
Application Response has two default settings: MaxElapsedTime and
MaxReportedTime. These settings are each defined as 60 minutes (one hour).
They are purposely very high so that you can detect and troubleshoot
transactions that take longer to complete than they should. Application
Response applies these time limits when monitoring all transactions for all
applications on all client systems (where AR agents reside). If a transaction
exceeds the MaxElapsedTime or the MaxReportedTime, Application Response
206 BTStudio Administration Guide