Specifications

How Transaction Limits Work
resources
{
require any
{
resource Process {ExecutableName="IEXPLORE"}
}
additional
{
resource Web { }
resource Windows { }
resource Connection { }
}
}
transaction "LoadPage"
module "LoadPage"
{
choice
{
event "WindowCreate" Windows Create { }
event "MouseClick" Windows MouseClick { }
event "KeyPress Windows KeyPress { }
}
event "BeginLoad" Web BeginLoad { Level="top" }
event "EndLoad" Web EndLoad { Level="top" }
}
Transaction-Specific Elapsed and Reported Time
You can set different time limits for each monitored transaction. To do this,
use BT Studio to edit the application rule set. Within the transaction definition,
use the same syntax as for an application-specific elapsed time or reported
time. Time limits are optional; you can set one, both, or neither time limit for
a transaction. A transaction-specific time limit overrides an application-specific
time limit.
Example of Transaction-Specific Time Limits
In this example, the Outlook rule set defines ReportedTime and ElapsedTime
for the application to be 15 minutes (900,000 milliseconds). These time limits
apply to the ForwardMessage and ReadMessage transactions, for which
transaction-specific time limits are not defined. The NewMessage transaction
definition specifies a ReportedTime maximum of 600,000 milliseconds; in this
case the application-specific ElapsedTime applies. The ReplyMessage
transaction specifies an ElapsedTime maximum of 300,000 milliseconds; in
this case the application-specific ReportedTime applies. The ReplyAllMessage
transaction specifies ElapsedTime and ReportedTime maximums of 100,000
milliseconds, which overrule both application-specific transaction limits.
208 BTStudio Administration Guide