MySQL slow_query_log logrotate\u00a0<\/span><\/h1>\n

---

\n

---

\n

We often enable MySQL slow_query_log<\/em> to proactively troubleshoot the performance, There is so lot of information with-in\u00a0slow_query_log\u00a0<\/em>which is enough to address most common (even complex ones occasionally) MySQL performance bottlenecks. What if we haven’t planned for the log lifecycle management of slow query log ? Your log will really grow huge (we keep long_query_time as-low-as 1 second), So we have to plan for slow_query_log<\/em>\u00a0rotating to avoid MySQL outage due to “no space left in the disk” to grow further. There are two ways you can do log rotate, I have explained below:<\/p>\n

\n
1. Manual log rotating (We use it only when there is an emergency)<\/li>\n
2. Using logrotate<\/strong>\u00a0to automatic MySQL log rotation (We love it, MinervaDB is an big fan of MySQL automation & DevOps. but we also recommend to use it very carefully)<\/li>\n<\/ol>\n
   \n

   \n

   Table of Contents<\/p>\n<\/i><\/a><\/span><\/div>\n