Enabling Resource Monitoring from the workbench

You can enable Resource Monitoring from the workbench to capture system resource data such as processor or memory usage.

To capture accurate resource monitoring data, you must ensure that the clocks on all computers are synchronized.
Note: If you do not synchronize the clocks on the workbench and on all of the computers involved in a test, resource counters will be displayed inaccurately (with respect to time) in the reports. (There are a number of tools that are available at no cost on the web to help you accomplish synchronization.)
  1. Open a schedule in the editor.
  2. In the Performance Schedule Details area, select the Resource Monitoring option in the Category drop-down list.
  3. Select the Enable resource monitoring check box.
    This activates the Data Source table.
  4. If this is a new schedule, the Data Source table is empty. If the resource monitoring data sources are available in the local schedule and you create the cloud schedule from it, the data sources are automatically added to the cloud schedule. Clicking Remove does not delete the data source from the file system; it merely removes it from this view. Other test schedules or applications might still use the data source.
  5. If you have existing locations in your workspace, you can click Add to add and configure them. If you do not configure the existing location, you are warned in the Data Source table that it is Not Configured.
  6. Select Ignore invalid resources when executing the schedule to suppress error messages about resource monitoring data sources. These errors can occur if the data sources are unreachable or invalid. If you select this option, you must view logs to see the error messages.
You have enabled Resource Monitoring from the workbench.
You must specify the data sources. Configuration changes that you make for a particular data source are stored with that location. This configuration storage means that you have to set up a data source only once. If you export a schedule, it contains the data source configuration information. This data might include potentially sensitive information, such as stored passwords.