Specifications

Failure Statement
Failure Statement
The failure statement defines events that, when they occur, indicate that the
transaction has failed in some way. You can define up to five failures for each
transaction. Application Response tracks this data and can report on the rate
of failures per transaction, or failure rates per client set or response endpoint.
Transaction failure data can appear in Trend, Top N, and At-a-Glance reports.
You can also view transaction failure details using the Agent Transaction
Viewer (ATV) from the eHealth Web interface. Failure statements must occur
at the end of a transaction definition, following the event specifications and
any except statements for the transaction.
Note: Some versions of Internet Explorer do not properly report 404 failures
or other types of browser failures. In these cases, Application Response cannot
report failed transactions.
Syntax
transaction "transaction- name"
module "module-name"
[
transaction- specific_constraints
]
{
event-specifications
}
except
{
except-event-specifications
}
failure1 "failure-name"
{
failure-event-specifications
}
failure2 "failure-name"
{
failure-event-specifications
}
failure3 "failure-name"
{
failure-event-specifications
}
failure4 "failure-name"
{
failure-event-specifications
}
172 BTStudio Administration Guide