LR monitoring MySQL via SiteScope

SiteScope Download, install

To monitor MySQL database performance using LoadRunner, LoadRunner does not provide the ability to directly monitor MySQL, so we need sitescope monitoring, and then LoadRunner show SiteScope monitoring results, This indirectly monitors MySQL performance.

It is hard to find sitescope on the way up, the HP official website after the revision cannot download the software. Fortunately, LoadRunner 9.5 comes with a SiteScope9.5. You can click to FTP (ftp://download.atstudy.com username/password: user1/user1) to download LoadRunner9.5. Download it and unzip it, load it into the virtual CD-ROM, andfind the Sitescope installation file in the "Additional components\sitescope\sitescope 9.50" directory.

2. Installing SiteScope

Please select for LoadRunner when installing, enter license number: pm90815892099998-99101472. After the installation is complete,

Will pop up a page, click on the Http://localhost:8080/SiteScope on the page. It will enter the SiteScope interface. When entering the interface, the display

Shown is the Red fork, you need to install the Java Runtime Environment Jre6, then run normally, you can also install the JDK directly

3. Download the Java version of the MySQL driver (the JDBC driver, and finally the 5 version above)

Unzip after download, copy the extracted Mysql-connector-java-5.1.14-bin.jar file

C:\SiteScope\java\lib\ext directory, whichever is your installation directory

after installing the system reboot (SiteScope is a software running in the browser, each time to open, just open the browser to enter the corresponding URL to enter the corresponding SiteScope main interface.

sitescope monitoring MySQL

1. Enter the SiteScope main interface, click "New Group", enter a custom group name, you can successfully add the group;

2. Go to the new group, click "New Monitor" under the new group, add monitor, monitor MySQL monitor Select "Database Counter";

3. Enter the Monitor settings:

Main settings:

Database connection url:jdbc:mysql://ip/database name;

For example: jdbc:mysql://206.168.191.19/abigdatabase;

Enquiry: Show status;

Database driver: org.gjt.mm.mysql.Driver;

4. Click "Get Counter", "OK" to save, so far, SiteScope has been able to monitor the data information;

5. Connect LoadRunner: Open LoadRunner Controller, add "SiteScope" in "Run", can successfully monitor the information of the database under test.

Appendix:

MySQL Common counters

Counter	Counter Analysis
threads_connected	Indicates how many customers are currently connected to the MySQL server, the number of connections is too many, the network is a problem, it is dynamic, when the maximum number of connections, the database system can not provide more connections, at this time, the program also wants to create a new connection thread, the database system will be rejected, If the program does not do too much error handling, there will be an error message
Threads_running	If the database is overloaded, you will get a value that is growing (the query's statement continues). This value can also be less than the pre-set value. This value is not a problem in a short period of time to exceed the limit value. If you exceed the preset and do not fall back within 5 seconds, monitor some other values at the same time
Aborted_clients	The value of the client being abnormally interrupted is not affected for some applications, but may be traced to other applications because an abnormally interrupted connection may indicate a problem with some applications
Questions	The number of queries that can be obtained per second, or the number of all queries.
Opened_tables	Indicates that the table cache does not have a hit quantity. If the value is large, you need to increase the number of Table_cache
Select_full_join	There is no execution of the primary key (key) union (join). The value may be zero. This is a good way to catch development errors because such queries can degrade the performance of the system
Select_scan	The number of full-table search queries performed. If you find that the value continues to grow, it means optimization, lack of necessary indexes, or other issues
Slow_queries	The number of queries that exceed this value (--long-query-time), or the number of indexed queries is not used. There is a small conflict for all queries. If the value grows, it indicates that the system has a performance problem
threads_created	This value is generally low. A higher value means that you need to increase the number of Thread_cache, or you are experiencing a persistent increase in connectivity, indicating a potential problem

LR monitoring MySQL via SiteScope