LR Monitoring Apache Resources

Tag: Cal cat problem: conf auto Runner status COM sys

The premise of this article is to use the Apache service that comes with LAMPP environment

Step 1, modify the Apache httpd.conf file, add the following code; file location:/opt/lampp/etc/httpd.conf, such as:

<Location/server-status>    SetHandler Server-status    Order deny,allow#    from all from  . localhost</Location>     

Note: The above code is in some httpd.conf files, just uncomment it.

Add the extendedstatus--behind the code if it is not, add it, and set the status to On

Extendedstatus on

Step 2, Uncomment

Uncomment the statement in the configuration file, the default is logoff under LAMPP

LoadModule Status_module modules/mod_status.so

Step 3, restart the Apache service

Step 4, verify success

Enter the following address for monitoring data (192.168.0.108 to native IP)

Http://192.168.0.108/server-status/?auto

Find the following error message, see figure:

Workaround:

1. Edit vim/opt/lampp/etc/extra/httpd-xampp.conf The file will be commented out require local under the file. Such as:

2. Restart Lampp,/opt/lampp/lampp restart

3, in the browser input http://localhost/server-status/?auto, verify if it appears as shown in the configuration is successful

Step 5, LR configuration instructions

Switch to LoadRunner controller to configure the monitoring target under Web Server Resource graphs, put the mouse in Apache view right click on select Addmeasurements, click Add, Enter the server IP address and server operating system. Such as:

After the run, the following is shown:

The following error message is sent after running:

Receive the following message from Monitor Name:apache. Parsing error, cannot find Token:cpuload. measurement:cpuload|192.168.0.108. hints:1) Such A measurement does not exist, or the HTML page is different from the supported one. 2) Try to replace the apache.cfg with appropriate apache_<version>.cfg file in <installation>\dat\monitors and    Rerun the application (entry Point:capachemeasurement::newdata). [msgid:mmsg-47479]

Error Analysis:

This is due to the fact that the counters that are being monitored for Apache are inconsistent with the LoadRunner default counters.

Workaround:

It is recommended that you close the controller and open the Apache.cfg file under C:\Program files (x86) \hp\loadrunner\dat\monitors (other file names are similar to Apache_<version>. CFG is a backup of the Apache monitoring configuration, only the apache.cfg is in effect):

1, modify counter0=idleservers for counter0=idleworkers, while modifying the annotation information label0= #Idle Servers (Apache) for label0= #Idle Workers (Apache), The description information is also proposed to modify;

2, modify counter4=busyservers for counter4=busyworkers, while modifying the annotation information label4= #Busy Servers (Apache) for label4= #Busy Workers (Apache), The description information is also recommended for modification.

3. Then save and close the file, reopen the controller and add the counter so that the monitoring is OK.

Run results if:

Other questions:

Workaround:

Modify the configuration file httpd.conf, modify the newly added content as follows:

<location/c-server-status>         SetHandler Server-status         Order deny,allow           from Nothing </location>           

Modify complete restart Apache service, OK

****************************************************************************************

Reference Documentation:

http://blog.csdn.net/jsship/article/details/43770311

http://blog.csdn.net/vikesgao/article/details/53693547

http://blog.csdn.net/wyingquan/article/details/538850

LR Monitoring Apache Resources