Specifications

Inaccurate Response Time Measurements
Troubleshooting 245
Response times are inaccurate
If a transaction's reported time is greater than expected, consider how you are
bounding the transaction rule. Have you specified appropriate starting and
ending events? Make sure that the final event specification correctly identifies
the end of the transaction. When calculating response time for a transaction,
BT Studio (or Application Response) includes the response time of all events
that occur from the start of the transaction to its ending event and that match
the resources listed (required and additional). In some cases, however,
application activity may match listed resources but may not be part of a
particular transaction, or you may not want to include the activity's response
time in the transaction's response time. For example, while a user is
performing a transaction, the application may also be performing some
background tasks. Because these tasks use the same resources as the
transaction and they occur during the time interval of the transaction, BT
Studio (or Application Response) includes the response time for the
background tasks as part of the total response time for the user's transaction.
To remedy this situation, use the IgnoreEvents clause as a filter to disregard
events (such as these background tasks) that might incorrectly affect the
response time measurements of monitored transactions. When Application
Response monitors a transaction, it omits any response time data for ignored
events from the transaction's total response time. Add the IgnoreEvents clause
to the additional resource definition for the application. Ignored events apply
to all monitored transactions for an application; you cannot specify events to
ignore for a particular transaction (that is, within a transaction definition).