MySQL App for Sumo Logic

MySQL, an open source Relational Database Management System (RDBMS), generates a variety of log files containing messages helping administrators to better understand the activities and errors occurring within their MySQL database.

Built specifically for MySQL, the Sumo Logic App for MySQL allows you to view the health of your servers without manual setup and delays. It will show you which servers have been stopped, the error log types over time, top errors, top warnings, crash recovery attempts over time, and the count of how many times a server has been up or down in a specific time window.

In addition, you can view MySQL replication details such as replication events that have been stopped and started, replication statuses over time, replication failures over time, and top reasons for replication failures.

MySQL log files can be daunting and time-consuming to analyze manually with the human eye, especially MySQL Error Logs which are single lines. Since a human may not be able to recognize patterns in logging activity, seeking an analytics tool like Sumo Logic can help make sense of MySQL log data. The Sumo Logic SaaS offering provides the following capabilities:

• Centralize and aggregate logs
• Create dashboards and monitor activity
• Create alerts and reports
• Apply advanced analytics to uncover patterns in log data
• Identify outliers and anomalies using machine learning
• >Monitor query performance and track slow queries, anomalies and changes over time

Check out the Sumo Logic App for MySQL to identify patterns of errors associated with slow queries and uncover other replication issues to improve the performance of your MySQL database server. It is included with your free trial of Sumo Logic for 30 days. Register now to get started!

Slow Query Logs. These contain SQL statements taking longer than a configured amount of seconds known as the “long_query_time” parameter value to execute and that require atleast the minimum number of rows to be examined known as the “min_examined_row_limit” parameter value.

Prior to MySQL 5.7.2, only the first line contained a time stamp for lines that occurred at the exact same time, however since then, all log lines now contain a time stamp. Check out the dev.mysql.com MySQL 5.7 reference manual for more details on MySQL Slow Query Logs.

MySQL Error Logs. These tell you when a mysqld was started and stopped and also records critical errors that occur during the running state of the server. Mysqld will write a message to the error log when it recognizes when a table might need to be automatically checked or repaired.

Also included in the Error Log message is an ID that corresponds to the thread in mysqld that is writing the message. The connection thread ID identifies the part of the server that produced the error message and exists both in the general query log and slow query log messages. For more information about the MySQL Error Logs, you can check out the dev.mysql.com MySQL 5.7 reference manual.