Online monitor graphs reference

The Graphs Tree displays the list of available online monitor graphs.

Tip: Graph names that are displayed in purple contain data. To only see the graphs that contain measurements, toggle the filter at the top of the tree from All to With Data. You can also search for a specific graph.

To select measurements to monitor in a particular graph, see the monitor configuration instructions for each specific monitor. For details, see Set up a monitoring environment.

The available graphs are described below:

Graph Category

Graphs

Runtime

The graphs provide runtime information about the scenario currently running.

For details, see Runtime graphs overview.

Transaction

The graphs provide transaction statistics and response times.

For details, see Transaction monitor graphs overview.

Web Resource

The graphs provide information on resource usage on the Web server during a scenario run.

For details, see Web Resource monitors.

Client-Side Measurements

The graphs provide information on client-side measurements:

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

For details, see Client-side Measurements.

System Resource

The graphs provide information about system resource usage.

For details, see System Resource monitoring.

Network

The Network Delay Time graph provides information on 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

The graphs provide 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

The Microsoft Active Server Pages graph provides 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

The graphs provide 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

The graphs provide 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

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

TruClient Native Mobile

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

Network Virtualization

The graphs provide information about Network Virtualization metrics:

  • Total Throughput

  • Average Bandwidth Utilization

  • Average Throughput

  • Packet Loss

  • Average Latency

For details, see Network virtualization monitoring.

SiteScope

The SiteScope graph 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.

Dynatrace

The Dynatrace SaaS / Managed graph provides data on the availability and performance of resources, processes and services in application environments measured by Dynatrace SaaS / Managed. For details, see Dynatrace SaaS and Dynatrace Managed monitors.

CA APM

The CA APM graph provides data for a web application monitor, to help you detect and diagnose performance problems in your complex or enterprise environments. For details, see CA APM monitor.

Application Deployment Solutions

The Citrix Server graph provides statistics about resource usage on the Citrix server during the scenario run. For details, see Application Deployment Solution monitoring.

Infrastructure Resource

The Network Client graph provides 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.

Microsoft Azure
The Azure Insights graph provides information on metrics collected from resources on the Azure Monitor Application Insights server. For details, see Azure Insights monitor.
Kafka

These graphs provide statistics about message flow and throughput between the Kafka broker and the producer or consumer during the scenario run.

The available graphs are:

  • Kafka Producer Duration

  • Kafka Throughput

  • Kafka Message Rate

For details, see Kafka monitoring.

Service Virtualization

The Service Virtualization graph provides information on metrics from the Service Virtualization Operations and Services monitors. For details, see Service Virtualization.
Infrastructure Testing Infrastructure Testing includes the Controller and Load Generators monitor graph. This graph displays the system resource usage of the Controller and load generator machines. For more information, see Controller and Load Generator Resources monitor.

To select measurements to monitor in a particular graph, see the monitor configuration instructions for each specific monitor. For details, see Set up a monitoring environment.

Back to top

See also: