Load Test Overview dashboard

When you use the Load Testing Integration to run load tests, you can analyze the
results that start in the Tagged Web Requests dashlet or use the Load Test
Overview dashboard.

1. Launch the dashboard from the Start Center. Select the Analyze
Performance item, and click Open load test overview link in the Analyze Load
Test Results section.
2. In the Dashboard Properties dialog box, select the data source: a stored
session or a System Profile.
The new dashboard prompts you for the data source. Select a System Profile if
you want to analyze the live session or select a stored session.
3. Analyze the load test result.
The top-left of the dashboard shows the Tagged Web Requests dashlet. All
other dashlets on that dashboard are linked with that dashlet. You must select a
test name (you can also multi-select). Data from the name or names you select
displays in the charts and the dashlets such as Transaction
Flow dashlet, Database dashlet, and Response Time Hotspotsdashlet. Use
this to analyze the root cause of tests that run slow.

Tagged Web Requests dashlet

Use the Tagged Web Requests dashlet to analyze tagged web requests.

The load testing integration allows you to specify a Timer Name. You can also display
additional context information such as Script Name, Test Name, or Virtual User.
Columns are added to the default view to display this information. The following figure
shows the Tagged Web Request dashlet with Test Name and Script Name added to
the default Timer Namegrouping.
Tagged Web Requests dashlet

Metrics

The following columns display by default to provide metrics for tagged web requests:

 Timer Name: The identifier for the web page, provided by a load test tool.
 Page Context: The identifier for a part of the web page, provided by a load test tool.
 Count: The number of times the web page has been rendered.
 Total Avg [ms]: The average overall time, in milliseconds, spent to render the web
page.
 Total Min [ms]: The minimum overall time, in milliseconds, spent to render the web
page.
 Total Max [ms]: The maximum overall time, in milliseconds, spent to render the web
page.
 Total Sum [ms]: The accumulated overall time, in milliseconds, spent to render the web
page.
 Avg [bytes] Sent: The average number of bytes sent as a response from the servlet.
 Min [bytes] Sent: The minimum number of bytes sent as a response from the servlet.
 Max [bytes] Sent: The maximum number of bytes sent as a response from the servlet.
 Sum [bytes] Sent: The accumulated number of bytes sent as a response from the
servlet.
 Avg [bytes] Rcvd: The average number of bytes received as a request to the servlet.
 Avg [bytes] Rcvd: The minimum number of bytes received as a request to the servlet.
 Avg [bytes] Rcvd: The maximum number of bytes received as a request to the servlet.
 Avg [bytes] Rcvd: The accumulated number of bytes received as a request to the
servlet.
 CPU Time [ms]: The average CPU time, in milliseconds, required to render the web
page.
 CPU Time [ms]: The minimum overall CPU time, in milliseconds, required to render the
web page.
 CPU Time [ms]: The maximum overall CPU time, in milliseconds, required to render the
web page.
  CPU Time [ms]: The accumulated overall CPU time, in milliseconds, required to render
the web page.

Grouping

You can set different levels of grouping to analyze the data in a number of different
granularities. You can select the groupings:

 From the grouping icons at the top right corner of the dashlet.
 Through the Group by option on the context menu.
 In the Analysis tab of the Dashlet Properties dialog box.

Several predefined groupings are provided as well as the option to define a custom
grouping.

Aggregation options

You can define the aggregation type in the Analysis tab of the Dashlet
Properties dialog box. Besides the predefined groupings, you can also define a custom
grouping by adding all columns that should be part of the grouping.

Transaction Flow dashlet

To open the Transaction Flow dashlet:

 AppMon 2017 May In the Cockpit, expand your System Profile and double-
click Transaction Flow.
 AppMon 2018 April In the sidebar, click Dashlets > Transaction Flow.

An overview of your environment appears. This includes the Agent Groups from which
you receive events.
Transaction Flow dashlet
The Transaction Flow dashlet supports different visualization modes that provide
different views and detail levels. The Topology View mode is the default mode. Use this
to analyze the basic operation. Use the Transaction Response Time view to analyze
transactions.

The dashlet header contains information about the current settings and data:

Transaction Flow dashlet - header

Visualization Mode Topology or Transaction Response Time view.

Business Transaction
Displays data based on a certain business transaction.
Filter

Total Transactions Number of transactions and average number of transactions per minute.

Number and percent of failed transactions in relation to the total number of

Failed Transactions
transactions.

Inter Tier Average latency time for transactions in milliseconds and total transaction
Time/Transaction execution time percentage.

The diagram consists of the following components:

 One or more entry points (generic, web request, synthetic request, browser, or user)
 Collapsible grouping frames for defined Agent Groups
 One or more database pools
 Inter-tier connectors or communication channels
o Blue: Incoming
o Green: Outgoing calls of currently select Agents
o Purple: A link shared between two selected Agents on multi-select

AppMon groups Agents by Agent Group. The System Profile specifies the Agent Group.
If your system landscape consists of many Agents, the collapsed view only shows the
Agent Groups, and not each single Agent. To switch between the collapsed and
expanded views, use the context menu. To access the context menu, double-click an
Agent Group or click the symbol in the upper right corner of the Agent Group. If an
Agent Group contains only one Agent, the group is always expanded and you cannot
collapse it. In order to prevent the Transaction Flow from exploding an upper limit of 100
Agents per Agent Group was introduced. Agent Groups that contain more than 100
Agents cannot be expanded.
The Transaction Flow diagram layout is organized around Agent Groups and not,
necessarily, physical hosts. You can use a single Agent Group, but it is recommended
that you configure your System Profiles with multiple Agent Groups that fit your
landscape. This helps with management and configuration changes and creates
meaningful diagrams.

Transaction Flow icons

Legend for Transaction Flow icons

View modes

Currently the Transaction Flow visualization supports the following view modes:

Topology view

Use the Topology view for a general overview of your application and the flow of
transactions. It shows the rate of calls and the protocols between tiers, as well as the
inter-tier time.
This view identifies which application components communicate with each other, how
many calls they make, the call rate, protocols, and the latency impact. This information
is based on all the PurePaths in the current live-session, per default, and unfiltered.

The diagram shows the call rate on communication channels between Agents and the
inter-tier latency time, if you enable it in the header.

Hover over the component and use the shortcut menu for detailed information on each
component in the diagram. The tool tips contain a subset of the details available in the
shortcut menu and provide quick access to the most relevant data. Component values
are bold face in the Transaction Flow visualization.

Transaction response time view

Use the Transaction Response Time view to analyze individual transaction types. In
magnified view, it shows the response time per transaction, protocol contribution, and
detailed call statistics per transaction or passing transaction.

This view analyzes single transactions and their flow through the application landscape.
Use it to trace a single type of transaction and identify which components contribute to
the execution of that transaction type. This information helps to identify bottlenecks and
resources used. You must zoom in on a flow to see transaction response times in
Transaction response time view.

The diagram shows the number of transactions that pass through a communication
channel, and the average calls per transaction on that channel. It also shows the inter-
tier latency time, if you enable this.

Zooming

You can use zoom in reduced and normal view mode using the mouse wheel and the
dashlet actions.
Differences in zooming view modes
Topic Normal view mode Reduced view mode

Contents

The Normal view mode visualizes hotspots using The low-resolution mode visualizes
Hotspot different font sizes to the response time hotspots using different font sizes to
contribution. the Agent Group name.

Does not show detailed information

Visualized Shows detailed information about Agent, Agent
about the Agent, the Agent Group,
Data Groups, and their connection.
and their connection.

Health visualization

Every Agent and Agent Group has its own health status.
AppMon visualizes this with a segmented health circle that contains the following:

 Process
 Host and transaction health
 Three states:
o Red: The host or process is unhealthy, or transactions are failing.
o Green: Everything is okay.
o Grey: No transactions are available, or the host or process is unknown.
Values visible in Transaction Flow

This section discusses the values in the Transaction Flow. You can't see all the detail
values in both the Topology and Transaction Response Time views. The values in the
Agent or communication link that is currently selected are in bold face.

The following terms are found throughout the Transaction Response Time view:

 Per Transaction: The value calculated is based on the overall transactions to which the
dashlet filter applies. The dashlet header displays the number of total transactions.
 Per Passing Transaction: The value calculated is based on the transactions between
two Agents or Agent Groups.

Inter-tier communication channels

Inter-tier communication is the communication between two Agents, typically the

different tiers of your application. Inter-tier time is the time (network latency, non-
instrumented tiers, and queuing) spent between two Agents: One Agent's last PurePath
measure point and another Agent's first measure point.

Call Details Description

Number and percentage of transactions that passed through the

Passing Transactions
communication channel in relation to all transactions.

Calls per Passing

Average number of calls invoked per passing transaction.
Transaction

Inter-Tier Response Time Inter-tier time impact on the overall transaction response time during the
Contribution specified time frame.

Calls Average number of calls per passing transaction, per overall transaction.

Average response time of a communication channel's end point per call,

Response Time
per passing transaction, per overall transaction.
Call Details Description

Average inter-tier time per call, per passing transaction, per overall
Inter-Tier Time
transaction.

Total number of calls and call per minute, sent over a communication
Calls
channel, and the percentage of different protocol contributions.

Agent Groups Agent Groups involved in this communication.

Agents Agents involved in this communication.

Entry communication channels

Entry communication channels typically mark a PurePath entry point.

Call Details Description

Passing Number of transactions invoked on this entry point per minute during the
Transactions/min specified time frame.

Transaction Response Average transaction response time or average server response time, if
Time browser diagnostics is not used.

Total number of invoked transactions during the specified time frame or in

Passing Transactions
the live session.
Database communication channels

Database communication channels represent database calls made by your applications.

Database Call Details Description

Executions / min Number of executions per minute.

Acquisition Time /
Average time per transaction for a connection acquisition.
Transaction
Database Call Details Description

Number of transactions that pass into the database and the percentage
Passing Transactions
in relation to all transactions.

Executions per Passing

Average number of executions per transactions for this database.
Transaction

Executions Number of executed database queries.

Response Time Average time for connection acquisition and query execution.

Acquisition Time Time for connection acquisition

Total amount of executions and the percentage of different protocol

Executions
contributions.

Instances Database name / SID and database host

Type Database vendor / type

Agent Groups Agent Groups calling the database

Agents Agents calling the database

Agents

Each connected Agent that contributes data to the current session, time frame, or filter,
has an icon that contains the Agent name, host name, and technology. AppMon groups
Agents by grouping frames, according to the System Profile configuration. The grouping
frames details are similar to the Agent, but show aggregated values.
Agent Details Description

Execution Time / Average execution time spent on this Agent or Agent Group per overall
Transaction transaction.

Transaction Response Percentage of time this Agent contributes to the overall average
Time Contribution response time.

Number of failed transactions and the percentage in relation to the total

Failed Transactions
number of transactions.

Passing Transactions Number of transactions that passed this Agent.

The average number of calls per passing transaction and per overall
Incoming Calls
transaction.

Average response time of this Agent per call, per passing transaction,
Node Response Time
and per overall transaction.

Average execution time on this Agent per call, per passing transaction,
Execution Time
and per overall transaction.

The total amount of calls made on this Agent and the percentage of
Incoming Calls
different protocol contributions.

Platform Technology on which the Agent runs.

Agent Full Agent name (all Agents in this group on Agent Group details).
Agent Details Description

Agent Group to which the Agent belongs (name of Agent Group on Agent
Agent Group
Group details).

Time Details

Overview of the min, max, average, sum, and percentage of the

Response Time
response time for all calls of an Agent or Agent Group.

Overview of the min, max, average, sum, and percentage of the

Execution Time
execution time for all calls of an Agent or Agent Group.

Overview of the min, max, average, sum, and percentage of the CPU
Execution CPU Time
(execution) time for all calls of an Agent or Agent Group.

Overview of the min, max, average, sum, and percentage for the
Database Time
database time of all calls of an Agent or Agent Group.
Database

Executed database statements display in one single aggregated view using the
database component. This view shows the number of executed database calls and their
execution time.

Database Details Description

Average time per transaction for connection acquisition and query

Response Time / Transaction
execution.

Transaction Response Time Percentage of time this database contributes to the overall average
Contribution response time.

Number of failed transactions and their percentage in relation to the

Failed Transactions
total number of transactions.
Database Details Description

Passing Transactions Number of transactions that passed this Agent.

Executions Number of executed database queries.

Database Response Time Average time of connection acquisition and query execution.

Database Time Time of query execution.

Acquisition Time Time of connection acquisition.

Executions Number of database queries executed.

Instance Database name or SID and database host.

Type Database vendor or type.

Time Details

Overview of the min, max, average, and sum of database execution

Database Time
time.

Overview of the min, max, average, and sum of database connection

Acquisition Time
acquisition time.
Third party calls

In installations that use User Experience Monitoring, AppMon visualizes user actions
with third party content using Third Party nodes. The third party calls value is the
average response time per call. AppMon does not apply these times to overall response
time calculation, because most of the third party calls run asynchronously.
External services

AppMon detects and visualizes server side transactions, like external service calls, in
the Transaction Flow dashlet. Amazon Web services, Microsoft Azure Cloud hosted
services and other non-instrumented processes are visualized to the right of the
Transaction Flow. External messaging calls are part of the external call detection and
are also visualized.
AppMon groups external service calls by top-level domain names (or cloud service
types, if applicable) and groups of such services are named according to their hosts.
External service call detection is performed by the .NET and Java Web Request
Sensors.

Work with Transaction Flow

Hover over Agents, Agent Groups, or communication links, to see drilldowns for root
cause analysis.
The example below displays an architectural problem: A call directly from the front end
to the database. Use the drilldown from the communication link between the front end
and database to go to the two affected transactions and analyze them.
The Transaction Flow legend shows that 12 failed transactions and highlights the
Agents and nodes in red. The Agent's details show the number of failed transactions
and the direct drilldown to errors on this node. The Errors dashlet shows errors and
drilldowns for analysis.
Drill down to monitor the health of your applications or to show which database calls are
made from a selected node.
 Looking for the 6.5 version of this page? Open in 6.5 documentation
On this page

 Transaction Flow icons

 View modes

 Zooming

 Differences in zooming view modes

 Health visualization

 Values visible in Transaction Flow

 Work with Transaction Flow

Related pages

 Follow your transactions with Transaction Flow

Application monitoring in AppMon Web

 Transaction flow web view

 Watch and learn

 Working with charts

 Exploring the transaction flow

Get topic updates

RSS feed Feedly

Last documentation build: