This section describes the various Performance Center monitoring components, and how to configure them to monitor a performance test.
Each monitor has different configuration requirements that are explained in the specific monitoring
All of the monitors allow you to view a summary of the collected data at the conclusion of the performance test. Using LoadRunner Analysis, you can generate a graph for any of the monitors. For details, see the LoadRunner Help Center (select the relevant version).
The online monitors are divided into the following categories:
|Run-Time||Display the number and status of Vusers participating in the scenario, as well as the number and types of errors that the Vusers generate.|
|Transaction||Display the transaction rate and response times.|
|Web Resource||Provide information about the number of Web connections, throughput volume, HTTP responses, server retries, and downloaded pages at the Web servers during performance test run.|
|System Resource||Measure the Windows, Linux, Server, and SNMP resources used during a performance test run.|
|Network||Display information about the network delays on your system.|
Measure statistics related to the firewall servers during the scenario run.
|Web Server Resource||Measure statistics related to the Microsoft IIS and Apache Web servers during the performance test run.|
|Web Application Server Resource||Measure statistics related to the Microsoft ASP application servers during the performance test run.|
|Database Server Resource||Measure statistics related to the SQL server, and Oracle databases during the performance test run.|
Measure statistics related to network virtualization, such as Packet Loss and Latency.
Measure statistics related to HPE Service Virtualization, per operation and service.
Use the SiteScope monitor and its counters to measure resources. For information, see the documentation provided with SiteScope.
J2EE & .NET Diagnostics Monitors
Provide information to trace, time, and troubleshoot individual transactions through J2EE Web, application, and database servers. For details, see the HPE Diagnostics User Guide.
Measure statistics related to the Citrix MetaFrame XP server during a performance run.
Provides information on the availability and performance of software applications and the impact on user experience measured by Dynatrace.
Provides information on the availability and performance of software applications and the impact on user experience measured by the New Relic Digital Intelligence Platform.
Configure the online monitoring environment
Specify the machines and measurements that the Controller will monitor during performance test execution in the Test Resources module. During performance test execution, the collected measurement data appears in the online graphs.
Configure the monitoring environment on the server machine
To use the following monitors, you must first install or configure monitoring components on the server machine. For details about configuring the monitoring components, see the specific monitoring sections.
Configure the monitors
To obtain performance data for a monitor, you need to configure the monitor (from the monitor profile), and indicate which statistics and measurements you want to monitor.
For information about selecting the servers to monitor and selecting the measurements to monitor, see Create and configure monitor profiles.
For details about each monitor's default measurements, refer to the relevant reference section for the monitor.
Monitors affected: Windows Resource, Microsoft IIS, Microsoft SQL, or Microsoft Active Server Pages
This error can occur when:
Configuring a monitor (when you click Get counters), or
During a test run (for example, if you have created a monitor profile and then change the Performance Center system user and run the test). An error is displayed in the Errors window and no data is displayed in the monitor's online graphs.
The Performance Center Server sends messages to the monitored server using the SMB2 protocol. This protocol uses the supplied user credentials for the session initialization, but the monitored machine sends another authentication request to the client, and the client sends the credentials of the user who runs the process that initiated the connection—the Performance Center system user account (IUSR_METRO by default).
If that user account does not exist on the remote server, authentication fails and the user that is being used for authentication and metrics retrieval is the one whose user name and password are provided in the Performance Center user interface when creating the monitor (when entering the server name and credentials in the Monitor Profile configuration).
If the Performance Center system user account exists on the monitored server, but is not a local admin on the remote server (or does not have the required permissions), the initial authentication succeeds, but retrieving the metrics from the remote server fails because the credentials provided in Performance Center when creating the monitor are not being used.
Remove the Performance Center system user from the monitored machine, or
Deny access of the Performance Center system user to the monitored machine from Local security policy > User rights assignment > Deny access to this computer from the network.