Monitoring system resources

When you apply load to a system under test, the system's resources are consumed increasingly. If the capacity of the resources does not match the load, you can see a performance degradation issues in the results. With the Resource Monitoring Service, you can continually observe the health of the system's resources while a schedule is running.

You can use the Resource Monitoring Service to capture data, such as processor or memory usage, while running a schedule or to monitor the availability of hosts and services. The Resource Monitoring Service can provide a comprehensive view of a system under test, to help determine problems. Hosts and services can be virtual machines, or any local host or network services. You can also monitor remote hosts and services with agents.

Monitoring local host and service

You use the Resource Monitoring Service to monitor any local host and network service. In this case, you can monitor with the local sources. This method is used for monitoring hosts on which monitoring agents cannot be installed.

Monitoring remote host with monitoring agents

You can use the Resource Monitoring Service to monitor remote hosts and services with agents through wider sets of collectors, computers, and networks to capture CPU load, disk space, memory, and the running process. Agent-based monitoring comes in handy when remote services are not directly accessible through the network.

Setting up agents
Agents are closer to the target that you want to monitor. The configuration task is simplified, and no security changes are required. You can set up the agent on an authorized host when access to an Apache httpd or NGINX server's status page or to a JVM JMX port is restricted to one or few client hosts only.

Requirements for monitoring resources with agents

The service does not require access to the agent host but the agent must reach the service host over HTTPS.

For Linux Performance monitoring, the agent must run on the Linux target.

For Windows Performance monitoring, the agent must run on the Windows target or on a Windows host that is configured to access the performance monitoring data of the Windows target.

You can monitor the performance statistics for the following data sources:

  • Apache httpd server

    To monitor the performance of the Apache web server resources, you can add the Apache httpd server data source to the Resource Monitoring Service. For example, if you want to view the throughput, request rates, and the CPU usage of the Apache server, you add it as a monitoring source.

  • NGINX and NGINX Plus

    To monitor the performance of NGINX or NGINX Plus server resources, you must add the NGINX server as a source to the Resource Monitoring Service.

  • Java Virtual Machine

    To monitor Resource Monitoring data from a Java Virtual Machine (JVM), you must configure the JVM source and add it to the Resource Monitoring Service. You can monitor JVM resources from a local or from a remote system.

  • Windows Performance host

    To check the performance statistics of the Windows host during a test run, you can add the Windows Performance host source to the Resource Monitoring Service. A Resource Monitoring agent is mandatory to get a Windows Data Collector.

  • Linux Performance host

    To check performance statistics of a Linux host during a schedule run, you can add the Linux host source to the Resource Monitoring Service. A Resource Monitoring agent is mandatory to get a Linux Data Collector.

  • Docker host

    You can monitor data extracted from a Docker host to analyze its performance statistics during a schedule run. A Resource Monitoring agent is mandatory to get a Docker Data Collector. The Docker host source is added to the list of resource monitoring sources when the agent is installed.

To monitor a resource, you must first add the source of the resource monitoring data to the Resource Monitoring Service. You must then select the performance counters to monitor the local sources.

If you monitor a host across monitoring agents, you must first install the Resource Monitoring agents on the target host for which you want to collect the performance statistics. The agents establish a connection with the Resource Monitoring Service. The new source is automatically added to the list of sources. You can select it in the list, choose its counters and view the live performance statistics.

Adding Resource Monitoring sources

You can monitor the performance of NGINX or NGINX Plus server resources, Apache web server resources, Docker host resources, or the performance of a JVM to check the performance statistics of the host source while a schedule is running. But you can monitor additional Resource Monitoring sources if you have Resource Monitoring agents running on a Windows or Linux host. To monitor these sources, you must add them to the Resource Monitoring Service.

Before you begin

You must be logged in and be the owner of an existing new project.

The project owner must have configured the Resource Monitoring sources.

If you monitor a remote host, it must be connected with the computer that you use to access Resource Monitoring Service.

If HCL OneTest™ Server is installed on a Linux system, by default, the Linux host source is displayed in the Resource Monitoring source list. If HCL OneTest Server is installed on a Windows system and you want to check the performance of the Linux host, you must have installed the Resource Monitoring agent on the Linux system.

If HCL OneTest Server is installed on a Windows system, by default, the Windows host source is displayed in the Resource Monitoring source list. If HCL OneTest Server is installed on a Linux system, and you want to check the performance of the Windows host, you must have installed an agent on the target Windows host to start monitoring its performance.

To allow remote access to the performance data on Windows 10, you must have considered the following information:
  • The user name and password are the same on the local and remote servers. Otherwise you must have provided remote server credentials.
  • The remote user must be a member of the Performance Monitor Users group (start lusrmgr.msc and add the user to this group).
  • The Remote Registry service must be running or automatic on the remote host (start services.msc and must have verified the Remote Registry status).
  • File and printer sharing must be enabled on the Network Interface of the remote host that is implied in communication with the local host.
  • The remote firewall is not blocking access; the following Windows Firewall rules must be activated:
    • File and Printer Sharing (NB-Name-In)
    • File and Printer Sharing (NB-Session-In)
    • File and Printer Sharing (*)

About this task

From the Resource Monitoring Service, you can add the Resource Monitoring sources and select the counters that capture the performance statistics. You can monitor a local host or a remote host. The remote host can be monitored through agents that are installed on the target host and connected to the Resource Monitoring Service.

Procedure

  1. In the Resource Monitoring page, add a source from Add a source, for example: Add an NGINX server.
  2. In the New server dialog box, enter the following information:
    1. In Target host, enter the IP address or host name and port number of the host where the server is installed.
    2. In Server edition, select the appropriate server from the drop-down list.
    3. In Path to the status page of the server, enter the name of the page to view the status of the server.

      If you select NGINX Plus (with API version 3) as a source, you must specify the name of the path to view the API root of the NGINX Plus server.

    4. In Security, select the following options:
      Secured with TLS/SSL
      If the application server is secured with TLS/SSL.
      Trust self-signed certificate
      To accept the server certificate.
      Do not verify host name
      To ignore verification of the host name in the certificate.
      Require credentials
      If the server requires login credentials, enter a User name and Password.
      Add a source
      Notes: If you added a JVM as the source to be monitored, you must enter the target host name, the port number, and optional credentials.
  3. Click Add.
  4. Select the resource counters to monitor. You can select them from the list where they follow the server logical organization.
    Choose Data Counters page
    For a faster selection, select the counters from the built-in sets drop-down list where they are organized by theme and save your selection.
    Choose data counters with the filters
    Note:
    For Docker host, you can select different sets of counters:
    • The first level of counters: Generic counters that are related to a Docker Image and all its running Docker Containers (in an exit, running or paused, created, restarted, removing, dead or transitive state).
    • The second level of counters: Specific counters that are related to the existing Docker Containers.

    The following tables show the total number of sources in your project and the number of sources ordered by type.

    Tables of available sources
  5. To view the Resource Monitoring live overview, use the links from the Total Sources and All Types tables.

    A properties table and a chart display the live performance for the first counter among the selected ones. To view the performance data of resource counters that are not shown by default, use the drop-down list. From the Counters column, you can change the resource's counters selection in the dialog that opens. You can select or deselect counters. From the Actions column, you can change the source parameters or delete them. The changes are reflected in the resource monitoring graph.

    Live performance statistics

Feedback