Use of mysql monitor MONyog and mysql monitor monyog

Use of mysql monitor MONyog and mysql monitor monyog

MONyog is a commercial paid software, but you can find the cracked version. I use the 4.72 cracked version.

1.

Fig 1.1

In the server settings, 1.1. Enable sniffing in Sniffer Settings? Select YES to enable Sniffer, and then setFilteringOptions,The Long Running Query Options Option; in the Long Running Query OptionsIn Actionto be taken, you can select notification, kill, notification, and kill query. If you select "kill", the query process can be automatically killed after the maximum time specified by the query is exceeded, thus killing the stuck process.

After Sniffer is started, you can analyze and view the Sniffer query in the query analysis. The value is 1.2.

Fig 1.2

 

 

2.

Fig 2.1

Select SSH connection in SSH Server Details, provided that the Linux Server starts the SSH service. After enabling the SSH service, you can monitor the status information of the Linux Server 2.2 in the Dashboard.

Fig 2.2

 

I personally think that Sniffer has a high availability to kill the process when the process is stuck. It can clear the previous stuck process. After using SSH, you can have an intuitive understanding of the historical status of Linux servers.

3. WaybackMachine can view the number of historical Mysql Server threads and the number of slow queries, 3.1. The Time Distribution of yesterday's slow query is displayed, and the information of the three slow queries is listed below.

Fig 3.1

The log files queried by the monitoring 151 test database server yesterday cannot be obtained because the slow query and general query log records are not enabled. Because the log files become longer with time, files will become more and more important, affecting the performance of the Mysql server. By default, the Mysql server is closed, so the corresponding log files cannot be obtained.

But sometimes to check the server's query needs to be opened, open the command:

SET GLOBALlog_output = file;

SET GLOBALgeneral_log = ON;

Set global slow_query_log = ON;

Because of the system variable changes, you can view the changes in Wayback Machine, 3.2.

Fig 3.2

4. After the Mysql Log function is enabled, you can configure MONyog to analyze Mysql logs. 4.1. Configure the path of the Mysql Log File in MoNyog and read the log through SFTP.

Fig 4.1

After the Mysql Log File is configured in MONyog, you can view the analysis result of MONyog on the log file in the query and analysis. 4.2 is the analysis result of the general query log.

Fig 4.2

5. In the deadlock settings, enable monitoring deadlock, 5.1

.

Fig 5.1

After the monitoring deadlock is enabled, you can view the deadlock in Monitor, as shown in. If the deadlock is detected, the deadlock information is displayed.

Fig 5.2

6.6.1 shows the Monitor tab. Monitor continuously monitors important attributes of the Mysql database server ., The left side is the server attribute group, and the right side is the status of the attributes of the selected group. Red points, yellow points, and white points are displayed in the figure. When the group's attributes exceed the threshold, a yellow point is displayed. When the group's attributes exceed the threshold, a red point is displayed, indicating a red warning, white points are normal values. The attribute marked with the bell symbol indicates that when the value of the attribute exceeds the threshold value, the email prompts a change. Click the graphic symbol on the left to display the data in the form of a chart, which makes it easier to understand the differences between data and data.

 

Fig 6.1

The Events tab is shown in 6.2. When any server property generates a yellow alarm or a red alarm, it is recorded as an Events. The Event table can preview all Events, you can turn the Event on or off. When the warning is cleared, the Last seen status is displayed, and the red or yellow warning values can be found in Monitor.

Fig 6.2