Specifications

Chapter 3: Generate an Event Log File
After you install BT Studio, you are ready to generate an event log file. To do
this, you use the target application (the application whose performance you
want to monitor) to perform transactions. The recording agent stores
information about all application activity in the event log file. You will later use
the event log file when using BT Studio to develop rules to recognize the
desired transactions.
This section contains the following topics:
Helpful Hints for Recording Events
(see page 35)
Record Events and Annotate the Log
(see page 36)
Transfer the Event Log File
(see page 38)
Open an Event Log
(see page 39)
Helpful Hints for Recording Events
Before you begin to record events, follow these suggestions to simplify the
rules development process:

Clear the cache. Before starting the recording agent, clear the cache as
follows: From the Internet Explorer browser window, select Tools, Internet
Options. On the General tab, in the Temporary Internet Files area, click
Delete Files and then click OK in the confirmation box. This procedure
prevents timing issues in the resulting event log file.

Use BT Marker. Before performing a significant step of a transaction (such
as a starting step or an ending step), use BT Marker to annotate the event
log. This helps to clarify the boundaries (start and end points) of a
transaction, which can be useful when defining rules with BT Studio. It
also helps you to identify the events in which you are interested. The
event log file contains lots of detail and, without BT Marker annotations,
you may have difficulty locating the desired events.

Pause between steps. As you perform a transaction, pause after each
action required to perform the transaction. This pause allows the
application to complete any processing required for that action before
starting the next action. These pauses, along with the BT Marker
annotations, can make it easier for you to identify and locate significant
events of a transaction.

Pause after the final step. Pause at least 30 seconds after performing the
final step of a transaction. After you think the application has finished
processing, use BT Marker to make a notation indicating the end of the
transaction.
Generate an Event Log File 35