Specifications

Failure Statement
failure5 "failure-name"
{
failure-event-specifications
}
Parameters
failure1, failure2, failure3, failure4, failure5
Required to define failures for transactions. You can define up to five failures
per module. Each failure statement begins with the failure keyword, which is
appended with a number 1 through 5.
If you need to define more than five failures, use a choice statement to group
several failure methods into a single failure case.
failure-name
A descriptive name for the failure case. These failure names do not appear in
Application Response reports, but they can appear in BT Studio and in the
Agent Transaction Viewer (ATV) of the eHealth Web interface. Use the same
guidelines as for transaction names and module names.
failure-event-specifications
Event specifications for the events that lead up to a particular failure. This
might be one event or a complex sequence of events. Each failure case must
begin with (repeat) the starting event for the transaction. This can be followed
by any number of event specifications that define the failure, including nested
choice and sequence statements. However, you cannot use a last statement or
other failure clauses within a failure statement.
When monitoring Internet Explorer transactions, you can use the Web
FailedLoad event to identify the failure messages displayed by Internet
Explorer.
Example 1: The following Login transaction definition consists of two events:
the event begins when the window title is "Login" and it ends when the
window title is "Login Succeeded". If these two events occur, Application
Response measures and records the total response time. The transaction
definition also defines a failure: the Login transaction has failed if the Login
window is followed by a window whose title contains "Login Failed". If these
two events occur, Application Response does not measure response time for
the Login transaction; however, it adds to the count of failed Login
transactions. The number of failed Login transactions can appear in various
eHealth reports.
BT Language Reference 173