LoadRunner Log Information

There are two types of logs
1. Log after running in Vugen
2. Log after running in controller

The log settings are in two steps:
1. First, run-time setting in the Vugen or controller, select Always send message, and then select Extended Log-data returned by server. This allows you to see the server Returns the information.
2. Select the log file path.
For logs generated after Vugen run, log files are placed in a USR file directory, ending with. log and. txt, for example Mdrv.log, output.txt
For the controller's log file, you can set the file location in Results>>results settings

There are two types of logs
1. log after running in Vugen
2. Log after running in controller
The log settings are in two steps:
1, first, in the Vugen or controller run-time setting, select Always Send
Message, and then Select Extended Log-data returned by server. So you can see
To the information returned from the server.
2, log file path for the log generated after Vugen run, the log file is placed in the same directory as the USR file
(such as: ... \mercury interactive\mercury loadrunner\scripts\login
), ending with. log and. txt, such as Mdrv.log, output.txt;

Lr_log_message will only send information to the Mdrv.log file, and Lr_output_message will

Write in the above two files.
For controller log pieces, Results>>results settings can set the file
Location and view it in the set directory when you view it. In the controller, many friends will want to know more

iteration, the parameters are imported correctly, we still look at log, we see the results after the execution is finished

The log folder of the directory, if it is run by the load generator, in the TMP directory. However, I also want to remind my friends

We also have to set the runtime settings in the controller, and each user group's

runtime settings, set by: In the controller's Design tab, the lower-right corner of the

Part of the Runtime Settings button, we click on it, set the same method as in the Vgen.

LoadRunner Log Information