Runtime graphs

Runtime information about the scenario currently running.

View graphs

• User Defined Data Points. Displays the real-time values of user-defined data points. You define a data point in your Vuser script by inserting an lr_user_data_point function at the appropriate place (user_data_point for GUI Vusers and lr.user_data_point for Java Vusers).
• Error Statistics. Provides details about the number of errors that occurred during each second of the scenario run. The errors are grouped by error source—for example, the location in the script or the load generator name.
• Vusers with Errors. Provides details about the number of Vusers that generate errors during scenario execution. The errors are grouped by error source.
• Running Vusers. Provides information about the status of the Vusers running in the current scenario on all load generators. The graph shows the number of running Vusers, while the information in the legend indicates the number of Vusers in each state.

For details, see Runtime graphs overview.

Transaction graphs

Transaction statistics and response times.

View graphs

• Transaction Per Second (Passed) by Location. Shows the number of successful transactions performed per second (y-axis) as a function of the elapsed time in the scenario (x-axis), broken down by location.
• Transaction Per Second (Passed). Shows the number of successful transactions performed per second (y-axis) as a function of the elapsed scenario time (x-axis).
• Transaction Response Time by Location The average transaction response time (y-axis) for each of the virtual locations with which the transactions were performed (x-axis).
• Transaction Response Time. The average response time of transactions in seconds (y-axis) as a function of the elapsed time in the scenario (x-axis).
• Total Transactions Per Second (Passed).Shows the total number of completed, successful transactions per second (y-axis) as a function of the elapsed scenario time (x-axis).
• Transaction Per Second (Failed, Stopped) by Location. Shows the number of failed and stopped transactions per second (y-axis) as a function of the elapsed scenario time (x-axis), broken down by location.
• Transaction Per Second (Failed, Stopped). Shows the number of failed and stopped transactions per second (y-axis) as a function of the elapsed scenario time (x-axis).

For details, see Transaction Monitor Graphs Overview.

Web resource graphs

Resource usage on the Web server during a scenario run through the following graphs:

View graphs

• SSLs per Second. The number of new and reused SSL Connections (y-axis) opened in each second of the scenario (x-axis). An SSL connection is opened by the browser after a TCP/IP connection has been opened to a secure server.
• Connections per Second. The number of new TCP/IP connections (y-axis) opened and the number of connections that are shut down each second of the scenario (x-axis).
• Connections. The number of open TCP/IP connections (y-axis) at each point in time of the scenario (x-axis). One HTML page may cause the browser to open several connections, when links on the page go to different Web addresses. Two connections are opened for each Web server.
• Retries per Second The number of attempted Web server connections (y-axis) as a function of the elapsed time in the scenario x-axis). A server connection is retried when the initial connection was unauthorized, when proxy authentication is required, when the initial connection was closed by the server, when the initial connection to the server could not be made, or when the server was initially unable to resolve the load generator's IP address.
• WebSocket Statistics. Statistics for the WebSocket data during the scenario run, such as byte rate, connection status, and the number of messages.
• Pages Downloaded per Second. The number of Web pages (y-axis) downloaded from the server during each second of the scenario run (x-axis). This graph helps you evaluate the amount of load Vusers generate, in terms of the number of pages downloaded.
• HTTP Responses per Second. The number of HTTP status codes—which indicate the status of HTTP requests, for example, "the request was successful," "the page was not found"—(y-axis) returned from the Web server during each second of the scenario run (x-axis), grouped by status code. You can group the results shown in this graph by script (using the "Group By" function) to locate scripts which generated error codes.
• Bytes Sent per Second. The number of bytes sent by the Vuser to the server per second.
• Throughput. The amount of throughput on the Web server (y-axis) during each second of the scenario run (x-axis). Throughput is measured in bytes and represents the amount of data that the Vusers received from the server at any given second. You can compare this graph to the Transaction Response Time graph to see how the throughput affects transaction performance.
• Hits Per Second. The number of hits (HTTP requests) to the Web server (y-axis) as a function of the elapsed time in the scenario (x-axis). You can compare this graph to the Transaction Response Time graph to see how the number of hits affects transaction performance.

For details, see Web Resource monitors.

Client-Side measurements

The following client-side measurement graphs:

• Page Load Event duration
• Page DOMContentLoaded Event duration
• DOM interactive

For details, see Client-side measurement graphs.

System resource graphs

Information about system resource usage.

View graphs

• UNIX Resources. The UNIX resources measured during the scenario. The UNIX measurements include: average load, collision rate, context switch rate, CPU utilization, incoming packets error rate, incoming packets rate, interrupt rate, outgoing packets error rate, outgoing packets rate, page-in rate, page-out rate, paging rate, swap-in rate, swap-out rate, system mode CPU utilization, and user mode CPU utilization.
• Windows Resources. The NT and Windows 2000 resources measured during the scenario. The NT and Windows 2000 measurements correspond to the built-in counters available from the Windows Performance Monitor.
• SNMP. Statistics for machines running an SNMP agent, using the Simple Network Management Protocol (SNMP). The x-axis represents the elapsed time. The y-axis represents the resource usage.

For details, see System resource monitoring.

Network graphs

Network Delay Time. The delays for the complete path between the source and destination machines (for example, the database server and Vuser load generator). The graph maps the delay as a function of the elapsed scenario time. For details, see Network Delay monitoring.

Web server resource graphs

Information about Web server resource usage:

• Microsoft IIS. Server statistics as a function of the elapsed scenario time. The x-axis represents the time that has elapsed since the start of the scenario run. The y-axis represents the resource usage.
• Apache.Statistics about the resource usage on the Apache server during the scenario run. The x-axis represents the time that has elapsed since the start of the scenario run. The y-axis represents the resource usage.

For details, see Database Server Resource monitoring.

Web application server graphs

Microsoft Active Server Pages. Statistics about the resource usage on the ASP server during the scenario run. The x-axis represents the time that has elapsed since the start of the scenario run. The y-axis represents the resource usage. For details, see Web Application Server monitoring.

Database server resource graphs

Information about database server resource usage:

• Oracle. Information from Oracle V$ tables: Session statistics, V$SESSTAT, system statistics, V$SYSSTAT, and other table counters defined by the user in the custom query.
• SQL Server. The standard Windows resources on the SQL server machine. The x-axis represents the time that has elapsed since the start of the scenario run. The y-axis represents the resource usage.

For details, see Database Server Resource monitoring.

MQTT Statistic graphs

Statistics about MQTT message flow and throughput between the MQTT broker and the client during the scenario run. For details, see MQTT Statistics monitoring.

Streaming State Statistic graphs

Provide statistics about the streaming videos in the scenario run. For details, see Streaming State Statistics monitoring.

TruClient native mobile

Statistics about CPU utilization memory on a mobile device during a scenario run. For details, see TruClient - Native Mobile monitors.

Network virtualization

Information about the Network Virtualization: Average Latency, Packet Loss, Average Throughput, Average Bandwidth Utilization, and Total Throughput. For details, see Network virtualization monitoring.

SiteScope graphs

Displays statistics about the resource usage on the SiteScope machine during the scenario run. The x-axis represents the elapsed time. The y-axis represents the resource usage.

These monitors can also be used to monitor Siebel and other ERP/CRM systems. For more information, see SiteScope Technical Specifications.

Dynatrace graphs

Provides data on the availability and performance of resources, processes and services in application environments measured by Dynatrace AppMon (see Dynatrace AppMon monitor) or Dynatrace SaaS / Managed (see Dynatrace SaaS and Dynatrace Managed monitors).

CA APM graphs

CA APM graph. A Web application monitor that lets you detect and diagnose performance problems in your complex or enterprise environments. For details, see CA APM monitor.

Application deployment solutions

Infrastructure resource graphs

Network Client graph. Statistics for FTP, POP3, SMTP, IMAP, and DNS Vusers on the network client machine as a function of the elapsed scenario time. For details, see Infrastructure Resources monitoring.

Service Virtualization graphs