KPI, Page, Transaction and Test Case Graphs

During the test run, every agent collects datapoints and sends them to the controller. If the agent runs in the application mode, it displays graphs with performance metrics collected on the agent. Since the agents are most likely operated on unattended computers, agent graphs and progress monitors can be viewed via Remote Desktop sessions. 

The controller communicates with the agents, collects, and displays graphs with aggregated real-time performance metrics. 

Note: The number of datapoints on the agent graphs can be slightly higher than the number of datapoints on the controller graphs. This is normal behavior caused by the limitation of the network bandwidth.

Load Agent Performance Counters

Every agent in application mode displays graphs of its local performance counters, such as CPU and memory utilization. By default, the Controller does not collect such Agent Performance Counters. If you wish to display agent computer performance counters on the controller, make sure to add them to the controller when configuring the test.

Test Report

After test completion, the controller generates a consolidated summary and detailed reports that include information aggregated from all agents. The Test report is stored on the controller. It can be reopened from the Test Results section.

Agent Report

After test completion, each agent generates a summary and detailed reports that include all information collected on this agent. Each agent report is stored on the corresponding agent in an SQL CE file. To open it, follow the directions described here.


Agent reports are only available for tests that used SQL CE for their test result storage.

Test Log

If the SQL Server CE is used as a repository, every agent will create its own database file locally for every test run. HTTP session information is stored in the test log on a machine where such sessions were initiated. You can query the test log as described in the Querying Test Log section. However, the controller can not query a remote agent’s database. Therefore it cannot query a portion of the test log generated by the VUs, instantiated on agents. The VUDetails report shows on which test machine every VU was instantiated. 

If the SQL Server is used as a repository, a single database, shared between the controller and all agents is used.  You can query the entire test log.

  • No labels