Specifications

Measure Response Time
EventLogFile registry setting. To change EventLogFile for the AR agent, use
the Configure Agent function of the eHealth Web interface. To change
EventLogFile for the BT Recording agent, use regedit to navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Firstsense\Firstsense and change its
value.
Important! Be careful when using regedit to change registry settings. If you
are not familiar with regedit, contact Technical Support before attempting it.
Size of the Event Log File
By default, the event log file has a maximum file size of 3 MB to prevent it
from consuming too much disk space. When the file reaches this size, the
recording agent creates a new event log and saves the old file with the suffix
.old (for example, events.btl.old). The old file also consumes a maximum of 3
MB, so you need to have at least 6 MB of file space for the event log file. When
the second event log file fills, the agent overwrites the existing .old file with a
new version of the .old file, and starts a new .btl file.
To change the default maximum file size, change the MaxEventLogSize
registry setting to specify the maximum size in bytes. If you are using the AR
agent with recording enabled, use the Configure Agent function of the eHealth
Web interface to change the value of this setting. If you are using the BT
Recording agent, use regedit to change it.
Changing Agent Settings for the Event Log File
When you change one of these agent settings, you do not need to restart the
agent. The new settings take effect almost immediately (within one or two
minutes).
Measure Response Time
A transaction definition in a rule set identifies the key application events that
characterize the operation. In addition to these key events, a transaction is
likely to include other events. These other events may be relatively
insignificant (such as key presses and button presses) or more significant but
not critical to identifying the transaction (such as request/response exchanges
with an application server). In any case, all application events that occur
between the first and last key events of a transaction (as identified by the
transaction definition) and that originate from the required and additional
resources identified in the application's resource definitions are included in the
response time calculation for the transaction. Key events have no special
significance in the computation of a transaction's response time.
Note that some events (such as GUI events) are instantaneous, while other
events (such as a request/response pair) are not. The combined durations of
22 BTStudio Administration Guide