On the Load Test Report page under the Log tab, you can review session details, like start time, duration, and execution status, in addition to other metrics.


The Start/End Time filters let you specify the time interval to view only the sessions started or running during this period of time. Sessions that finished earlier than Start Time and started later than End Time will be filtered out. By default, the filters use the time of the test beginning and end.

The Status filter allows you to display only the sessions with the following details:

  • All. All test sessions.
  • Success Only. Sessions with successfully executed tasks.
  • Failures Only. Sessions with errors occurred while task executions.

In some cases, you may not find any sessions under the Log tab while your test is successfully completed. Or you may see less sessions then you expected in the log. If that occurs, select the Include Uncompleted Sessions option to display sessions with an Uncompleted status. By default, we do not include statistics on uncompleted sessions into the error statistics and session log. If the option is activated, uncompleted sessions that were automatically stopped by LoadView will be displayed in the log. To find more details on why a test session can be stopped and how to work with them, see the Uncompleted Sessions article of our Knowledge Base.

If the Only Reference Load Injector option is selected, the Reference Load Injector Server sessions will be displayed in the list.

The reference user executes a task simultaneously with virtual users simulated on our Load Injectors (LIs). Therefore, you can compare reference and LI sessions running at the same time interval in terms of duration compliance; the duration shouldn’t differ significantly. Further, in the case of Web Application and Web Page tasks, you can play the video of the reference session execution to track the application and page behavior under the load.

To filter sessions started on the LIs, the following filters are available:

  • Zone. Allows filtering by the geographical location the sessions were started from.
  • Agent. Allows filtering the session list by LIs the sessions were started on.
  • User ID. Allows filtering by a particular virtual user ID.

To display or edit Zone, Agent, or User ID filters (if configured), click View next to the filter field.

Viewing session details

To view session steps in detail, expand the session header.

To play the video of a reference session, filter the list by Only Reference Server, and then click the video link in the session description header.

To view a session Performance Report, click the details link next to the session description.

On the session report page, click the Errors Only toggle to display failure details only.

To view a description of an error in the sessions list, point to the failure status in the corresponding column. You can also find an HTTP(S) task body under the Body link in the failed session description.

The most common reasons that could lead to errors in a test are the following:

  • Errors in the test configuration. In the case of a web application test, check the device configuration.
  • CPU overload on LI servers. Check the CPU usage chart on the Summary tab.
  • Client-side errors such as hardware/software infrastructure and application issues.

See also: Error Codes