Share this page

# Collate scenario run results

This topic describes how to collate results during or after a scenario run, and to define the data types to collate.

Tip: You can set a command that runs once collation is complete. Select Tools > Options > Execution tab, and enter the command in the Post Collate Command box.

To configure results collation:

1. Select Results > Collate Results > Collate Settings.

2. In the Collate Settings dialog box, define the data results that you want to include in the collated results, in addition to the transaction data. By default, all are selected.

   The following options are listed:

   - Transaction data. This is non-editable, the transaction data is always included in the collation.
   - Vuser logs. Includes Vuser log file data from the run.
   - NV. Includes Network Virtualization data related to the run.

3. When Auto collate results is enabled, Controller automatically collates the raw data from the load generators, either during or after the run. If the raw data is collated during runtime, there is a faster processing of the results at the end of the run.

   Note:

   - Controller must be connected to the load generators for automatic collation to occur.

   - The Vuser logs and NV data are always collated at the end of the test, not during runtime.

   Select an option for where and how you want collation to occur:

   - At the end of the test The raw data is automatically collated at the completion of the scenario run.

   - At runtime to Controller. (Default) The raw data is collated during runtime and sent to Controller. You can set the following additional export options:

     - Automatically export results to InfluxDB. During runtime, the collated data is also exported to an InfluxDB database. Click the InfluxDB Settings link to check the connection is set up. For details, see Export data to InfluxDB or JSON.

     - Automatically export results to OneAnalysis. During runtime, the collated data is also streamed to the OpenText Core Performance Engineering Analysis database. Click the Settings link to check the connection is set up. For details, see OpenText Core Performance Engineering Analysis integration.

   - At runtime to Data Hub. The raw data is collated during runtime and exported to the Data Hub.

     Define the relevant Kafka Topic name for the Data Hub.

4. Click Save.

5. If you select to collate the results manually (by disabling Auto Collate Results), then at the end of the scenario run you can manually collate the results. Select Results > Collate Results > Collate Resultsto collate the data types selected in the Collate Settings dialog box.
6. The Collate Results dialog box is opened at the end of the scenario run to view collation progress, if relevant. For details, see Collate Results dialog box.
7. If you need to stop the collation process, in the Collate Results dialog box, click Stop. To resume the collation process, select Results > Collate Results > Continue stopped collation.

If collation fails due to a lack of disk space:

You can trigger re-collation by selecting Results > Collate Results > Recollate.

Controller attempts to collate the results again, without compressing the .eve file.

### See also

- Collate run data
- Data Hub and Web Connector setup

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1-26.3 All View Local Help Center View Online Help Center Version: