Specifications

Event Types
identifying the key events that must be matched for Application Response to
recognize and monitor a transaction.
Syntax
event event-name event-type event-action { parameter-list }
event-name
Required. The event name is a non-unique name that you assign and use to
identify the event in the events pane of the main BT Studio window. It is
useful when debugging rule sets. The event name can consist of any character
string and has no impact on the recognition of transactions. You must enclose
the event name in quotation marks.
event-type
Required. The event type identifies the resource from which the event
originates. Possible values include: AppEvent, Connection, DNS, Java, Outlook,
Process, Session, Windows, and Web. Event types specified in transaction
definitions must correspond to resource types specified in the resource
definition.
event-action
Required. The event action specifies the kind of action to observe. The set of
possible values depends on the event type.
parameter-list
Optional. A parameter list is a comparison expression used to match an event
with greater precision. For more information, refer to Parameter List.
Event Types
In the BT language, each event specification describes a single application
event. The event type identifies the resource from which the event originates.
Possible values include: AppEvent, Connection, DNS, Java, Outlook, Process,
Session, Windows, and Web. Event types specified in transaction definitions
must correspond to resource types specified in the resource definition.
AppEvent Event Type
Use the AppEvent event type to define events sent by the user of the
Application Event API.
BT Language Reference 123