Specifications

Track Failed Transactions
Open Top Ten Alarms Transaction
transaction "TopTen"
module "TopTen"
{
event "TopTenStarted" Java JMouseRelease { Title=contains:"eHealth Live
Exceptions" Text="Top Ten Alarms" }
event "TopTenWindow" Windows SetTitle { Title="Top 10 Alarms" }
last
{
event "TopTenDone" Java JSetLabel { Title="Top 10 Alarms" }
}
}
failure1 "Exception"
{
event "TopTenStarted" Java JMouseRelease { Title=contains:"eHealth Live
Exceptions" Text="Top Ten Alarms" }
event "Exception" Windows SetFocus { Title="LiveHealth Internal Error Messages" }
}
Track Failed Transactions
To understand the end-user experience, you must measure the following
facets of application performance:

Availability: Is the application available when users need it? Measure
application availability using SystemEDGE with the Service Availability
module.

Response time: When users use an application, does it response quickly?
Use Application Response to measure actual, observed response times
experienced by end users.

Failures: Are users able to successfully complete transactions? Transaction
failures occur when the application is available to users, but something is
preventing the transactions from finishing. These failures can significantly
degrade user productivity. Use Application Response to monitor the rate of
failed transactions. When the failure rate increases, you can use
Application Response to determine the most frequent cause of the failures
and then take steps to eliminate the cause and so restore user productivity
to normal levels.
Application Response tracks the total count of failures for each monitored
application and transaction. You can use Live Health to send alerts when the
failure rate suddenly increases dramatically, indicating an application problem
that needs to be resolved. You can also use the following eHealth reports to
monitor transaction failures:
Monitor Transactions in Java Applications 109