View OneAnalysis graphs

Use OneAnalysis graphs to help monitor and view the data displayed in the most effective way possible.

OneAnalysis graphs overview

The following graphs are available in OneAnalysis:

Report Name Description
Running Vusers graph

Displays the number of Vusers that executed scripts and their status during each second of the test.

Note: This graph is currently unavailable.

Throughput graph Displays the amount of throughput on the server during each second of the load test scenario run. Throughput is measured in bytes or megabytes and represents the amount of data that the Vusers received from the server at any given second.
Transactions graph

Displays the total number of transactions that passed, the total number of transactions that failed, and the total number of transactions that were stopped, during each second of a load test scenario run.

Note: This graph is currently unavailable.

Hits per Second graph Displays the number of HTTP requests made by Vusers to the web server during each second of the load test scenario run.
Average Transaction Response Time graphs Displays the average time taken to perform transactions during each second of the load test scenario run.

Back to top

View the Summary graph

This section describes how to view OneAnalysis graphs.

  1. Select a run to analyze as described in Select a run to analyze.

  2. The Summary page for the selected run opens, and displays the following information:

    UI Elements Description
    Run Time. The start time of the selected run

    Duration. The total time used by the selected run.

    Statistics
    Max Running Vusers

    The maximum number of Vusers that ran concurrently in the selected test tun.

    Total Throughput (bytes) The total throughput, measured in bytes, over the selected test run.
    Average Throughput (bytes/seconds) The average throughput, measured in bytes per second, over the selected test run.
    Total Hits The total number of hits over the selected test run.
    Average Hits per Second The average hits per seconds over the selected test run.
    Passed Ratio The ration of transactions that passed during the selected test run.
    Transactions
    Total The total number of transactions that passed and failed.
    Measurement Name The name of the measurement.
    Graph Minimum The minimum response time of each measurement appearing in the graph.
    Graph Average The average response time of each measurement appearing in the graph..
    Graph Maximum The maximum response time of each measurement appearing in the graph.
    Graph Median The median response time of each measurement appearing in the graph.
    Graph Std. Deviation The standard deviation of each measurement appearing in the graph.
    Percentage 90 The response time of 90% of transactions (90% of transactions that fall within this amount of time).
    Passed The number of transactions that passed.
    Failed The number of transactions that failed.
    Stopped The number of transactions that stopped.
    HTTP Responses
    Codes

    The HTTP status codes returned from the web server during the load test scenario run.

    For a list of HTTP status codes, see HTTP status codes.

    Total

    The number of times each HTTP status code was returned from the web server during the load test scenario run.

    Per Second

    The number of HTTP status codes returned from the web server during each second of the load test scenario run.

  3. Select a graph to display for the selected run.

Back to top

Known issues for OneAnalysis graphs

  • Granularity differences in Hits per second and Throughput graphs. Grouping is displayed differently in Hits per second and Throughput graphs, resulting in the data in the graph to be displayed differently compared to LoadRunner Analysis. While the number of hits and the total average is the same, differences can be seen for small intervals. For example, if you have data points with a time stamp of 1:10:13, 1:10:16, 1:10:18 and the starting point is 1:10:13, the InfluxDB considers 1:10:13 as a group and 1:10:16 and 1:10:18 as another group, instead of creating two groups, one containing 1:10:13 and 1:10:16, and the other containing 1:10:18.

Back to top

See also: