Share this page
Single user performance data
When enabled, you can collect client-side breakdown data to analyze user experience for a specific business process.
The NV Insights report
A comprehensive report based on the selected script that provides information about how your application performs for a specific business process.
After the test runs, the NV Insights report is available from the Single user performance reports page.
NV Insights report known limitations:
| Limitation description | Limitation |
|---|---|
| Load generators | Test must be configured to run on cloud load generators. |
|
Number of scripts |
You can specify one script per test to generate a client side breakdown report. |
|
Script type |
The following script types are supported:
|
| IP addresses | When using allocated IP addresses, an additional, dedicated IP address for the NV Insights report is required. For details, see Dedicated IPs. |
| Your script is configured to run with proxy settings that are inaccessible from outside your local network |
Client side breakdown widgets and report are not generated. Disable the proxy and run the test again. If the issue persists,submit a service request. |
| NV Insights report limitations |
|
Troubleshooting NV Insights report generation
- The report is generated for the location with the highest distribution of Vusers. If the distribution is spread equally amongst locations, a location is randomly selected.
- If emulation is specified, the report is generated for the network profile that has the highest distribution of Vusers.
- A report might not generate for the following reasons:
- The test duration is too short.
The script does not contain network actions.
Transaction response time breakdown data
When enabled, you can collect navigation timing data on up to five scripts to analyze user experience for a specific business process.
Scripts are run on the location with the highest distribution of Vusers. If the distribution is spread equally amongst locations, a location is randomly selected.
If emulation is specified, scripts are run on the network profile that has the highest distribution of Vusers.
Data is gathered for the following metrics for each transaction in the breakdown script:
| Metric | Description |
|---|---|
| Blocked |
Average amount of time for all HTTP(s) requests in the queue waiting for a network connection. |
| DNS |
Average amount of time taken for all HTTP(s) requests to resolve a host name. |
| Connect | Average amount of time taken for all HTTP(s) to create a TCP connection. |
| Send | Average amount of time taken to send an HTTP request to the server. |
| Wait |
Average amount of time taken for all HTTP(s) waiting for a response from the server. |
| SSL |
Average amount of time for all HTTP(s) requests to negotiate SSL/TLS. |
| Receive | Average amount of time taken for all HTTP(s) requests to read an entire response from the server (or cache). |
| Client |
The client time is the time spend by the browser to load resources, render them, execute scripts, and the idle time of the transaction. Idle time is any time spent waiting for user input or a user operation. It is actually the time taken to perform client side operations plus the waiting time for a trigger to end a transaction. Note: Transaction Response Time (TRT) included in Client Side Breakdown is different from TRT included in reports. In Client Side Breakdown, TRT includes Wasted Time, which is time spent during a transaction for internal functionality of the script engine. In reports, TRT does not include Wasted Time. |
