Use of MySQL monitor Monyog

Monyog is a commercial charge software, but can find a cracked version, I use 4.72 cracked version

1.

Figure 1.1

In the server settings, 1.1. Enable sniffing in sniffer settings? Select Yes to turn on sniffer, and then set filteringoptions ,Long Running Query Options In the long Running query options actionto be taken, you can choose to notify, Kill, notify, and kill queries. If you select Kill, the query process is automatically killed after the query has exceeded the preset maximum time, thus killing the stuck process.

After you start sniffer, you can analyze and view the sniffer query in query analysis, 1.2.

Figure 1.2

2.

Figure 2.1

Choose SSH connection in SSH server details, provided the Linux server initiates the SSH service. When the SSH service is turned on, you can monitor the status information of the Linux server in Dashboard 2.2.

Figure 2.2

Personally feel that the sniffer in the process of the death of the process is strong availability, you can clear the last time that the process of the card dead. With SSH, you can have a visual understanding of the history of Linux servers.

3. Waybackmachine can view the number of history threads and slow queries for MySQL server, 3.1. Shows the time distribution of the slow query yesterday, and lists the information for the three slow queries below.

Figure 3.1

Yesterday monitoring 151 Test Library server query log file can not be actually obtained, because there is no slow query, general query logging, because the log file over time, the file will be more and more affect the performance of MySQL server, the default is turned off, so also can not get the corresponding log file.

However, sometimes in order to detect the server query needs to open, open the command:

SET globallog_output = file;

SET globalgeneral_log = on;

SET GLOBAL slow_query_log = on;

As a result of changes to the system variables, in Wayback Machine can see the change, 3.2.

Figure 3.2

4. After you have turned on the MySQL log function, you can set up a log with Monyog to analyze MySQL. 4.1, configure the path to the MySQL log file in Monyog and read the log through SFTP.

Figure 4.1

After you have configured the log files for MySQL in Monyog, you can view the results of the MONYOG analysis of the log files in the query analysis. 4.2, for the General query log analysis results.

Figure 4.2

5. In deadlock settings, enable monitoring of deadlocks, 5.1

.

Figure 5.1

The condition that the deadlock can be viewed in monitor after a deadlock is turned on, as shown in 5.2. If a deadlock is detected, information about the deadlock is displayed.

Figure 5.2

The Monitor tab is shown in 6.6.1. Monitor can continuously monitor the important properties of MySQL database server. , the left side is a group of server properties, and the right side is the state of the currently selected grouped properties. You can see that there are red dots, yellow dots, white points in the graph, when the attribute in the group exceeds the threshold alarm to display a yellow point, when the attribute in the group is significantly above the threshold value is a red dot, indicating a red warning, the white point is normal; a property marked with a bell symbol that indicates that the message will change when the value of Clicking on the graphic symbol on the left shows the data in the form of a chart, which makes it easier to understand the differences between data and data.

Figure 6.1

6.2 is shown in the Events tab, when any property of any server has a yellow alarm or red alarm, will be recorded as an events, the event table can preview all occurrences, the event can be received open or closed, when the warning status display last Seen, red, or yellow warnings are able to find the corresponding value in monitor.

Figure 6.2

Use of MySQL monitor Monyog