Share this page

# Maintain system health

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

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

In this topic:

## View system health

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

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

Click the Refresh button to reload 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 OpenText Enterprise Performance Engineering system.

To perform a system health check:

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

2. Configure the system health check.

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

      UI Element | 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.
      Servers | Select all or the specific servers in the system to check.
      Hosts | Select all or the specific 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 | Select All to display all servers and hosts, or Selected to display the selected servers and hosts only.
      View standard or full list of health checks | Select Standard view to display the basic list of checks from the previous system check, or Health check view to display the full list of health checks. For details, see Health checks performed on server machines 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, Servers, or Hosts pane to see results of the system components that you included in the system check (indicated by passed or failed ).

   Move the Collapse All / Expand All switch to collapse or expand all the host panes.

   To filter the system check results to only display results with failed status, move the slider to Failed Only. Hosts that failed are given a Failed status and the number of failed results is listed.

   Health checks performed on server machines

   View | Description
   --- | ---
   Standard | Name. Name of the OpenText Enterprise Performance Engineering server. Status. Displays the status of the server (Operational, Non-operational, Unavailable) State. The runtime state of the server. Performance. Indicates whether the server performance check passed or failed. Configuration. Indicates whether the server configuration check passed or failed. Host Installation. Indicates whether the host installation performance check passed or failed. Connectivity. Indicates whether the server connectivity check passed or failed.
   Health Check | In addition to the server name, status, and state, it includes: Last Check. Time and date of the last health check. IIS. Checks IIS is installed and configured properly. Execution Management. Checks the Execution Management web service which displays the API for managing test run actions, such as start run, stop run, and cancel run. Lab Management. Checks the Lab Management web service. Load Test Management. Checks the PCSLoadTestManagement web service. ME Application. Checks the MeSyncAppService web service. Remote Management service. Checks connectivity between the server and the Remote Management Agent service. Backend Connectivity. Checks connectivity between the server and the Backend Service. Database Connectivity. Checks connectivity between the server and the database. User Identity. Checks the server user identity. Hosts Compatibility. Checks if the servers versions are compatible with the hosts. Hosts Connectivity. Checks connectivity between the server and hosts. Time Series Database. Check the Time Series databases on the hosts are accessible from the server. Passphrase. Checks the security passphrase. Time Settings. Checks the time settings for the database platform and server.

   Health checks performed on host machines

   View | Description
   --- | ---
   Standard | Name. Name of the host. Status. Displays the status of the host (Operational, Non-operational, Unavailable) State. The runtime state of the host; only. Location. The location of the host. Belongs to Pool. The pool to which the host is assigned. Purpose. Indicates the purpose for the host: Controller, Data Processor, or Load Generator. Over Firewall. Indicates whether the host is located over a firewall. Version. Lists the version of host.
   Health check | In addition to all Standard view checks, it includes: Last Check. Time and date of the last health check. Time Series Database. Checks the Time Series database is up and running. User Identity. Checks the host user identity. Server Connectivity. Checks connectivity between the host and servers. Load Generator Connectivity. Checks connectivity between the Controller and load generators Backend Service Connectivity. Checks connectivity between the host and the Backend Service.

4. Create a system health report.

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

   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 Elements | Description
   --- | ---
   Component Name | The name of the component on which check task was
   Description | A description of the task performed
   Start Time | Start time of the task
   End Time | End time of the task
   Result | A detailed description of the outcome of the task
   Passed | Passed or failed depending on the outcome of the task
   Status | Progress of the task

Back to top

## Schedule automated maintenance tasks

Scheduled automated maintenance tasks provide constant monitoring of the system's key components 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 Administration, click Maintenance > System Health.

2. Select the Maintenance Tasks tab.

   The following fields are available in the Maintenance Tasks tab.

   UI Elements | Description
   --- | ---
   Name | 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.
   State | Indicates the task state: Enabled or Disabled.
   Last execution time | The last time the maintenance task was performed.

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) Note: You can define an allow list of folder paths on the Controller by editing the LegalPaths.csv file, located in the <Server_installdir>\dat directory. These paths will be safely accessed by the ltopsvc process. Folder paths must be absolute paths. Only paths listed in LegalPaths.csv will be considered safe for access. Example: `C:\PerformanceTests\Results` `D:\ArchivedTests`
   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 OpenText Enterprise Performance Engineering 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 OpenText Enterprise Performance Engineering, 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

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