Specifications

How Transaction Limits Work
discards its response time information. The data is not included in any reports,
nor is it stored in the eHealth database. However, the transaction is included
in the count of timed-out transactions for reporting purposes (available
through the Transaction Timeouts variable).
If you want to change the MaxElapsedTime or MaxReportedTime settings, edit
each application rule set to define the ElapsedTime or ReportedTime
constraints (or both) at the application level or the transaction level. These
constraints override the MaxElapsedTime and MaxReportedTime settings. If
you do not define these constraints for some applications or transactions, the
MaxElapsedTime and MaxReportedTime settings still apply to them.
Application-Specific Elapsed and Reported Time
You can set different transaction time limits for each monitored application. An
application-specific time limit overrides the default time limits. To define an
application-specific transaction time limit, use BT Studio to edit the application
rule set. Before the resource definition, add the following syntax:
[
ReportedTime < milliseconds
]
or
[
ElapsedTime < milliseconds
]
Replace milliseconds with the maximum number of milliseconds. Time limits
are optional; you can set one, both, or neither time limit for an application.
When it observes a transaction whose response time exceeds an upper limit,
Application Response counts the transaction as "timed-out." If you define a
lower limit (such as ElapsedTime > 1000) and a transaction does not reach
this limit, Application Response discards its response time data.
Example of Application-Specific Transaction Time Limits
In this example, the rule set defines both ReportedTime and ElapsedTime to
be 15 minutes (900,000 milliseconds). Application Response counts as timed-
out transactions any monitored transactions (for this application) that exceed
15 minutes.
[
ReportedTime < 900000
ElapsedTime < 900000
]
BT Language Reference 207