MySQL

For monitoring systems, the strength of basic functions is indeed crucial, but how to implement them in different scenarios is even more critical. In the “Monitoring Practice” chapter, we collect various monitoring practice experiences, which will be categorized by different components. If you have good practical experience with a certain component, you are welcome to submit a PR and attach the link of your article to the corresponding component directory.

• Getting Started Tutorial for Monitoring MySQL with Categraf
• Building MySQL Monitoring According to the Guidance of Nightingale Template Center
• How to Detect and Handle MySQL Master-Slave Delay Issues
• Explanation of MySQL Monitoring Principles
• Monitoring MySQL with Exporter
• Solving the max_prepared_stmt_count Problem in MySQL

In addition to monitoring MySQL’s performance data, we can also customize SQL to monitor data in MySQL (which can be done through Categraf’s mysql plugin). This usually has two purposes:

• Extending performance monitoring metrics. If the default performance monitoring data is insufficient, this method can be used for extension.
• Monitoring business data. This scenario is extremely extensive, such as monitoring order data, user data, etc. This scenario is easily overlooked but can sometimes have surprising effects.