Transaction attributes
Transaction attributes
The ARM standard defines various different transaction attributes. The "Transaction attribute filter menu" shows the supported transaction attributes for filtering.

Figure: Transaction attribute filter menu
These attributes are described in detail in the following sections. A check mark indicates that the appropriate filter is active and the user can input filter data.
Arrival
The Arrival transaction time span defines the
duration from a transaction where it really begins in time until
the transaction was started within ARM. Please refer to the ARM
standard documents (, ) for further details on this attribute.

Figure: The transaction arrival filter
Blocked
The Blocked transaction time span defines the
duration where the transaction was blocked executing its tasks.
This time span is measured indirectly from the uses of the
blocked-API calls. Please refer to the ARM standard
documents (, ) for further details on this attribute.

Figure: The transaction blocked filter
Context properties
Context properties are user defined key/value pairs which can be associated to a transaction. The standard defines up to twenty context properties per transaction measurement. During registration of transactions the context properties have to be named. Therefore the MyARM-Manager knows for each selected transaction the defined context property names. As shown in "Context property menu" a menu is provided to enable or disables with appropriate context property filter widget. A check mark indicates that the appropriate filter is active and the user can input filter data.
"Context property
menu" shows all context property names of the
HTTP transaction of the apache web-server.
"Context property
filter widgets" shows the active and visible filter
widgets with user input. Each context property filter widget uses
the
string type widget .
![]() Figure: Context property menu |
![]() Figure: Context property filter widgets |
|
Figures: transaction context
property filter
|
|
Duration
The transaction Duration attribute filter is used
to filter transaction according to their duration (response time).
It is possible to show only transactions with a duration greater
than a specified value. It uses the
time span type widget which describes the supported operators
in detail.

Figure: The transaction duration filter
Start time
The transaction StartTime attribute filter is used
to filter transactions according to their start time. It is
possible to show only transactions which are started before or
after a specific start time as well as between two start times. It
uses the
time stamp type widget which describes the supported operators
in detail.

Figure: The transaction start time filter
Status
With the transaction Status attribute filter
transactions can be filtered according to their execution status.
The pull-down menu as shown in "The transaction status pull-down menu
filter" supports to select GOOD, FAILED, ABORTED or
UNKNOWN. Currently only one status or all together can be selected
at a time. It uses the enumeration
type widget .

Figure: The transaction status pull-down menu filter
Stop time
The transaction StopTime attribute filter is used
to filter transactions according to their stop time. It is possible
to show only transactions which are stopped before or after a
specific stop time as well as between two stop times. It uses the
time stamp type widget which describes the supported operators
in detail. In "The
transaction stop time filter" a calendar widget is
shown for easy entering a date.

Figure: The transaction stop time filter
URI
The transaction URI attribute filter is used to
filter transaction according to their associated URI if any. It
uses the
string type widget .

Figure: The transaction URI filter
User
The transaction User attribute filter is used to
filter transactions according to their associated user if any. All
known user names are presented in a pull-down menu as shown in
"The transaction user
filter" . It uses the enumeration
type widget .

Figure: The transaction user filter

