LoadRunner How to monitor system resources under Linux

LoadRunner How to monitor system resources under Linux

A period of time in the study LoadRunner process, in the stress scene test through the LoadRunner to real-time monitoring of Windows system resources, in the previous sections I have summed up the relevant process, in recent times found a group of friends asked how to monitor the Linux system resources, So I also built some Linux environment on this issue, and deployed a Web application under Linux to explain the stress test example, and summarized how to set up Loadruner to monitor Linux system resources in real time.

About LoadRunner monitoring Linux system resources is broadly divided into the following steps:

1, before monitoring Linux I would like to point out that the LIUNX system mechanism is similar to Windows, to monitor and get his relevant parameters must need to get its consent, this is the operating system, so you must have sufficient permissions and methods to obtain, About Linux is also associated with adding zones in LR, with Windows enjoying the same status. In Windows you need to open many permissions, as well as some remote access processes, currently in Linux is no exception, there is a process under Linux is required, That is the system daemon Rpc.restat, I believe that the Guardian process is not unfamiliar, usually in the boot of the Linux system to start a lot of services, these services are daemons, and it is out of the terminal in the background to run.

So first of all, to see if the system has RPC service turned on, command rpcinfo-p to see

As you can see, if four rstatd services are turned on, the RPC Daemon service startup is successful. If this service is not available, you will need to manually install the

:http://heanet.dl.sourceforge.net/sourceforge/rstatd/

Installation: One-time execution--TAR-XZVF rpc.rstatd-4.0.1.tar.gz//Unpacking the installation package

CD rpc.rstatd-4.0.1//Enter into the RPC.RSTATD directory

./configure//Configure RC.RSTATD Installation

Make//Edit RC.RSTATD

Make Install//install

2. Restart Port mapping Service Portmap

/etc/rc.d/init.d/portmap Start//Startup Portmap

Find the Portmap service on the OK

3, through the command rpcinfo-p to detect, as shown in the figure 1 shows that the service installation and start-up is successful.

4. Add Linux system resource entries in the LoadRunner scenario

One thing to note here is that when we first add the Linux resource Service, we may prompt the error message, prompting for the RPC service to add failure on the client, if you encounter this situation, you may also feel disappointed, do not worry, analysis of the cause of the error, basically can be determined that the remote did not get to the RPC service, Should be what was hijacked, to see the system firewall, cat/etc/sysconfig/iptables configuration, sure enough to join the RPC access policy, so I closed the Firewall service, so there is no need to set the firewall policy, the command is:

Chkconfig iptables on//Permanent boot firewall

Chkconfig iptables off//permanently shut down the firewall

After shutting down the firewall, add the Linux resources in the LoadRunner scene as shown in:

Seeing the graphs and graphs above indicates that the configuration is OK, we have made some progress in breaking LoadRunner.

LoadRunner How to monitor system resources under Linux