Maintain system health

The System Health page displays information about the LoadRunner Enterprise system health (including connectivity of LoadRunner Enterprise components and version alignment), and enables you to run a full validation on your LoadRunner Enterprise system. The Maintenance Tasks tab provides constant monitoring of the system's key components in order to detect system failures.

Note: The System Health module is not available to Tenant Admin users. For details, see Predefined admin roles.

View system health

To view information about the LoadRunner Enterprise system health in LoadRunner Enterprise Administration, click Maintenance > System Health > Health Check, and select the panel for the system component you want to view: Integrity (database), LoadRunner Enterprise Servers, or Hosts).

By default, the System Health grid displays the last known system health results for each component in your LoadRunner Enterprise system, including a description of the task, start and end time, task status (Passed, Failed, Warning), and task results.

Click to refresh the grid so that it displays the most up-to-date information.

Tip: It is recommended to use System Health on a monthly basis to verify the system validity, as well as after running remote installations or upgrades. If there is an issue with a specific host, use the Check Host function from the Hosts page.

Back to top

Perform a system health check

This task describes how to run a full validation on your LoadRunner Enterprise system.

To perform a system health check:

  1. In LoadRunner Enterprise Administration, click Maintenance > System Health, and select the Health Check tab.

  2. Configure the system health check.

    1. Click Check System and select which LoadRunner Enterprise components to include when doing a system check.

      Action Description
      Check Integrity

      Checks on the database that all servers and hosts have the same version, and the status of any Over Firewall hosts and MI Listeners.

      LoadRunner Enterprise Servers

      Select all. Alternatively, select the specific LoadRunner Enterprise servers in the system to check.


      Select all or the specific LoadRunner Enterprise hosts in the system to check.

      Note: The system check only displays hosts that are currently operational, in Idle state, and not over firewall. It does not check standalone load generators.

    2. You can perform the following actions to customize the display:

      Action Description
      Search Use the search box to search the servers or hosts list by name, and to show only those hosts that include the specified search string.
      Show selected servers and hosts only Move the All / Selected slider to display all servers and hosts, or the selected servers and hosts only.
      View standard or full list of health checks

      Move the Standard view / Health check view slider to display the standard or full list of checks from the previous system health check.

      For details, see Health checks performed on LoadRunner Enterprise Servers and Health checks performed on host machines.

    3. Click Check to perform the check.

      You can cancel a system health check at any time by clicking the Cancel Check button. The Check System button changes to Cancel Check after the health check starts. Cancelling is useful if an error is found early on in the checks where you have many hosts, and you do not want to proceed.

      After canceling a check, the Health Check page displays the last completed check, or remains empty if no checks were completed.

  3. View system health results.

    Expand the Integrity, LoadRunner Enterprise Servers, or Hosts panel to see results of the system components that you included in the system check (indicated by passed or failed ).

    You can move the Collapse All / Expand All slider to collapse or expand all the host panels.

    To filter the system check results to only display results with failed status, move the slider to Failed Only. Hosts that contain a failed status are indicated with a red line and list the number of failed results.

  4. Create a system health report.

    To export the results of the system check as a CSV or Excel file, click Export to CSV or Export to XLS .

    The report is generated and the CSV or Excel file is downloaded to your browser's download directory. When the download is complete, click the file name in the status bar to open the report.

    The report contains the following information for all tasks in the grid:

    UI Element Description
    Component Name

    The name of the component on which check task was


    A description of the task performed

    Start Time

    Start time of the task

    End Time

    End time of the task


    A detailed description of the outcome of the task


    Passed or failed depending on the outcome of the task


    Progress of the task

Back to top

Schedule automated maintenance tasks

Scheduled automated maintenance tasks provide constant monitoring of the system's key components in order to detect system failures. You use the Maintenance Tasks tab to check the status of the system.

To view information about maintenance tasks performed by the system:

  1. In LoadRunner Enterprise Administration, click Maintenance > System Health.

  2. Select the Maintenance Tasks tab.

    The following fields are available in the Maintenance Tasks tab:

    Field Description

    The type of maintenance check. For details, see the list below.

    Recurrence (min) The frequency of the maintenance task.
    Description A description of the maintenance task.


    Enabled or Disabled.
    Last execution time The last time the maintenance task was executed.
  3. Click the name link to view maintenance task details or to change the run frequency.

    The following table describes the maintenance tasks:

    UI Elements Description
    Resource Recovery Task

    Performs predefined validation tests on Controllers and load generators that are in the Non-Operational state. If the host passes the test, its status changes to Operational.

    • Controller validation tests. Tests the OTA connection, ability to run, and available disk space.

    • Load Generator validation tests. Tests the connection to the agent.

    The task parameters must be within the following guidelines:

    • MIN_APPLICATION_DIR_DISK_SPACE: Between 10 and 1000

    • CHECK_LG_TIMEOUT: Between 1 and 15

    • MAX_RETRIES: Between 1 and 1000

    Default frequency: Every 15 minutes

    Note: For load generators over a firewall, this is performed by the OFW Status Update task (see above).

    Result Cleaning Task

    Cleans test run results from Controllers or load generators in the following instances:

    • If the results have already been collated.

    • There are old performance tests whose results were not collated.

    • If the performance test was deleted.

    The RESULT_EXPIRY_DAYS task parameter must be between 1 and 1000.

    Default frequency: Every 360 minutes (6 hours)

    OFW Status Update Task

    Updates the real status (Operational or Non-Operational) of a host that is located over a firewall.

    Default frequency: Every 15 minutes

    Orphan Run Task

    Identifies orphan test runs during and outside of the active timeslot.

    Default frequency: Every 15 minutes

    Data Processor Task

    Sets and updates a data processing queue for any of the following actions: Analyzing a test run, recalculating the SLA, or adding test runs to a trend report.

    Default frequency: Every minute

    Check Host Task

    Verifies the host installation, and updates the host status to either Operational or Non-Operational.

    This task checks a predefined number of hosts on a rolling basis instead of checking all hosts simultaneously; this enables the task to run faster and puts less load on IIS and the LoadRunner Enterprise server.

    You can configure the following task parameters (click outside the Value field, and click Save to save your changes):

    • EXCLUDE_HOSTS. Enables you to exclude specific hosts from the task. List the host names exactly as they are written in LoadRunner Enterprise, separated by a semi-colon (;).

    • CONCURRENT_CHECK_LIMIT. Enables you to determine the maximum number of hosts that are checked concurrently. We do not recommend setting a value higher than the default (50); use a lower value if you experience slowdowns during the Check Host run.

    • Enables you to determine the maximum number of hosts that are checked concurrently

    Default frequency: Every 15 minutes (we recommend using the default value or a higher frequency to avoid putting excessive load on the system which can lead to performance degradation).

    Publish Runs For Trending

    Automatically add runs to trend reports.

    Default frequency: Every 60 minutes

    Check Timeslot Task

    Checks active timeslots and handles idle instances.

    Default frequency: Every 2 minutes

    Cloud Cleanup Task

    Cleans cloud related data.

    Default frequency: Every 15 minutes

    Cloud Update Task

    Updates cloud related data.

    Default frequency: Every 15 minutes

    Entity Unlocking Task

    Unlocks all locked entities (tests, scripts, timeslots, monitor profiles, monitors over a firewall, and analysis templates) that have not been updated after a specified amount of time.

    You can specify the amount of time, in minutes, after which the maintenance task unlocks any locked entity from the TIMEOUT_UNLOCK parameter. The default timeout value is 120 minutes.

    Default frequency: Every 120 minutes

Back to top