Introduction

The MyARM-Manager gives a MyARM user the ability to get an overview of measured transaction data via the MyARM agents (transaction response times as well as metrics, properties and so on). Overview in that context means to have graphical and statistical summaries of measurement data selected by the user. One of the major aims thereby is to be able to work fluently with a big amount of data (e.g. millions of transactions).

The MyARM-Manager is an integral part of the MyARM delivery and will therefore "automatically" detect which MyARM environment to use. For a further description on how MyARM is configured please refer to the users guide.

Figure: The MyARM-Manager welcome screen

When the MyARM-Manager is started the main window opens with a welcome screen as shown in "MyARM-Manager welcome screen". To browse through transaction measurements a so-called selection has to be opened using the Selections menu. The following section lists and describes briefly the available selections.

Selections

The MyARM-Manager provides the possibility to view measurement data regarding different aspects. This concept of having different views on the same data is called a "selection". A selection defines the way how to access and interprete transaction measurements. Currently the following selections are supported:

Definition selection

is used to view and analyse transaction measurements by selecting one or more different transaction definitions.

Tree selection

is used to view and analyse transaction measurement trees of one selected so-called parent transaction definitions.

Both selections provide a tree of all known application and transaction definitions on the left side of the main window. The user can select here the transaction definitions for further analysis.

For analysing the measurements MyARM-Manager provides different views on selected transaction measurements which can be opened by pressing the appropriate "view" button in the left bottom corner of the main window. The following section gives a brief overview of available "views".

Views

Views represent the way how transaction measurement are presented by the MyARM-Manager. Currently the following views are available:

Table or tree view

provides the ability to show single transaction measurements in a table or a tree. The user can browse through measurements and view all associated ARM metrics or properties.

Statistic view

provides a statistically overview of the currently selected transaction measurements including mean, minimum, maximum, median and deviation values.

Graph view

provides a scatter diagram of the currently selected transaction measurements. The X- and Y-axis can be choosen from different attributes of the transaction measurement.

Histogram view

provides a histogram over the response times of the currently selected transaction measurements.

Filtering

Since MyARM captures any transaction measurement within a database filtering is essential to get fast and concrete measurement information the user wants to know. Therefore the MyARM-Manager provides various different filters.

Transaction filtering

The main filter criteria is the transaction type (or in ARM words transaction definition) the user wants to dig into. For this purpose the MyARM-Manager provides an easy to handle tree of all known application and transaction definitions. At the top level of the tree the application definition is shown. Each application has its own set of transaction definitions which can be shown by opening the appropriate application definition node.

Transaction definition selection differs depending on whether a "Definition selection" or a "Tree selection" was chosen. The "Definition selection" supports multi-selection of transaction definitions where the "Tree selection" only supports single-selection of a transaction definition.

Attribute filtering

After the transaction definition is selected additional filter criteria can be choosen by selecting various attribute values of transaction measurements. Here is a brief overview of supported attributes which can be used for filtering:

Transaction status

status of an executed transaction (e.g. GOOD, FAILED, etc)

System address

the system (host) the transaction was executed on.

User

the user on behalf the transaction was executed.

URI

the associated URI of the transaction.

Context properties

User defined context properties (name/value pairs)

Duration

Duration (response time) of the transaction.

Arrival

Arrival time of the transaction (part of the duration).

Blocked

Blocked time of the transaction (part of the duration).

Start time

Start time of the transaction (in UTC).

Stop time

Stop time of the transaction (in UTC).

Defined filters

MyARM-Manager supports the storage of the currently selected filter attributes. This is called "Defined filters". A defined filter is associated with a name and saved for future use on the local hard drive. Such a defined filter can be activated just by selecting the associated name from a pull-down list.