Specifications

Filter Events
3. In the Open dialog box, use the Look In field to navigate to the directory
containing the desired event log file.
4. Select the file name or type it in the File name field.
5. Click Open.
6. Events recorded in the log file appear in the events pane of the BT Studio
window. Use the divider bar between the events pane and the rules pane
to expand the events pane.
7. Take a few moments to examine the information displayed in the events
pane. Each event is described on one line. For each event, BT Studio
shows a line number, the event type (such as Windows, Process, or
Connection), the event action (such as ButtonPress or MouseClick), and
more information about that event. Annotations created using BT Marker
appear on separate lines in the Engine State column. You will use this
information when developing rules.
Hint: When you first open an event log, test it against the default application
rules to make sure that BT Studio can recognize default transactions and that
you have the correct application rules enabled and displayed.
Filter Events
By default, the recording agent stores information about all activity performed
on the client system. As a result, the event log file may contain large amounts
of information, much of which may not interest you. BT Studio allows you to
filter the contents of the events pane to display, for example, only the events
for a specific application, or all events except those of a certain action type.
Filtering is powerful. It helps to reduce unwanted data from the event log file
or to focus your attention on the important or significant events. This can help
to streamline the process of defining rule sets.
Before filtering events, think carefully about the transactions you want to
define. Which application is involved? You can filter out all others. Which event
types or actions are important for rules development? Filter out those that do
not interest you. You should filter out any executables that are not listed in the
resource definition for the application. Hiding those executables will make it
easier to identify significant events for transaction rules.
You can filter the events displayed in the events pane based on the values of
any of the columns listed at the top. Filtering does not actually delete any
information from the event log file. Rather, it hides information from the
events pane, removing unwanted data from view while you define rules.
Note: The event filter only affects which events are displayed in the events
pane. It does not affect the processing of events in the event log file. When
you test rules, they run against all events in the log file, including events that
are not displayed in the events pane due to filtering.
54 BTStudio Administration Guide