> OctoPerf load testing - JMeter settings documentation page. How to configure the JMeter properties and reporting for this User Profile.

Source: https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/options/jmeter/

# JMeter

![User Profile JTL](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/user-profile-jmeter-configuration.png "User Profile JTL")

## Runtime Properties

![Runtime Properties](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/properties.png "Runtime Properties")

Defines the JMeter Runtime Properties. 

These key/value properties are initially defined here and can be modified while the test is running in the [Runtime Properties](https://api.octoperf.com/doc/analysis/edit-bench-report/runtime-properties/) panel.

!!! tip
    You can use these properties in your scripts with the syntax `${__P(name,defaultValue)}` (defaultValue is optional).

## JTL

![JTL](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/img/jtl-configuration.png "JTL")

Defines the JMeter Test Log file generation settings. The settings are:

* **Enabled/Disabled**: Toggle ON/OFF the JTL file generation,
* **Results Log Level**: Log all results, only errors or only successes,
* **Save Settings**: defines what information must be saved in the generated JTL files.

!!! note
    JTL files are available when the test ends in [the result logs panel](https://api.octoperf.com/doc/analysis/edit-bench-report/test-logs/). JTL files can be used for reporting in the [Jenkins CI integration](https://api.octoperf.com/doc/runtime/edit-scenario/integrations-automation/ci-cd/ci/jenkins/).

!!! info
    JTL files with same columns are automatically merged into a single file named `merged_X.jtl` once the test is finished. Depending on the size of JTL files, it may take a few minutes before the merged file is ready.
