Specifications

Inaccurate Response Time Measurements

Check the Recognized Events tab in the results pane. If it lists one or more
events for a transaction, BT Studio was able to begin to recognize a
transaction but was not able to recognize all of its events. Double-click the
first event. In the events pane, BT Studio jumps to the starting event for
the transaction. Scroll down the events in the events pane to find the
subsequent events that you expected BT Studio to recognize. Compare the
characteristics of these events with the event specifications in the
transaction rule. Update the event specifications to accurately reflect the
events to be recognized. Test your rules again using breakpoints and F10
to step through events to learn where the rules fail. Continue refining the
event definitions and transaction rules until BT Studio recognizes the
desired transactions properly.
Inaccurate Response Time Measurements
BT Studio (or Application Response) may calculate unexpected or seemingly
inaccurate response times for several reasons. In BT Studio, response time
measurements appear in columns of the Transactions tab on the results pane.
In Application Response, response time measurements appear in the Agent
Transaction Viewer and in reports.
No network or server time reported for transactions
If BT Studio does not report network time or server time for recognized
transactions, check to make sure that the additional section of the
application's resource definitions includes the connection resource, similar to
the following:
resources
{
require one
{
resource Process
{ ExecutableName=$(Application Executable) }
resource Process {ExecutableName="process_name"}
}
additional
{
resource Windows { }
resource Connection { }
}
}
You also may not see network and server time for a recognized transaction
because the transaction is local to the client system and does not include
server time. To ensure that BT Studio (and Application Response) can report
client, network, and server time for these transactions, temporarily define the
Bytes constraint as follows:
Troubleshooting 243