Specifications

Track Failed Transactions

At-a-Glance reports for response paths, client sets, and end points

Trend reports for individual response paths and groups of response paths

Top N reports for response paths, client sets, and end points
For each of these reports, you can monitor the rate of failed transactions and
compare it to the rate of successful transactions. (Use the Failed Transactions
variables when generating Trend and Top N reports.)
How It Works
To track transaction failures, you use BT Studio to modify the application rule
set to define one to five failure cases for each transaction. Application
Response tracks the total count of failures for each transaction. eHealth
reports show this information as the rate of transaction failures per minute.
Application Response does not, however, provide a breakdown of failures by
case. That is, if you define four failure cases for the Login transaction (such as
Invalid Password, Invalid Server, Server Not Available, and Cancel Login),
Application Response maintains a single count of all failures for the Login
transaction. The reports do not show a breakdown of Login failures based on
their causes.
If Live Health or eHealth reports reveal a sudden increase in transaction
failures, you can use the Agent Transaction Viewer (ATV) to troubleshoot the
cause of the failures. In the ATV, the transaction details indicate the reason
that each transaction failed, based on the defined failure cases.
To track transaction failures
1. Define failure cases:
a. Use BT Studio to define up to five failure cases for each transaction in
an application rule set. Defining failure cases requires that you
understand the causes of failed transactions and the events that
characterize them. If you have more than five failure cases for a
transaction, you can use the choice statement to combine multiple
failures under one failure case.
b. Test the updated rules against an event log file that contains
application activity for the failure cases.
c. Upload the updated application rule set to Application Response.
2. If you use Live Health, define a profile that raises an alarm when the
failure rate exceeds a threshold. (For instructions, refer to the online help
in the eHealth Web interface.)
3. Use eHealth reports and Live Health to monitor the number of transaction
failures.
4. If you notice a sudden increase in transaction failures, use the ATV to view
the details. The ATV shows the name of the failure case that applies to an
individual transaction. Use this information to determine which failure
110 BTStudio Administration Guide