Hello Schneider,
Thank you for posting question on Microsoft Windows Forum!
Based on the issue description. Well! A slow query log that grows unbounded and fills the disk, is a known limitation of MySQL. The core reason is that MySQL 8.0 does not include built-in rotation for the slow query log file. Unlike binary logs, which rotate automatically based on size, the slow query log is a plain text file that will grow indefinitely until you intervene. The "log rotation needs to be set up" message you are seeing is MySQL's way of telling you that the responsibility for managing that file lies outside the server itself. On the other hand, MySQL does not natively rotate its own text-based slow query log files based on file size. It expects the host operating system's utilities, specifically logrotate, to handle file management. Because this configuration is not set up by default in many base installations, the log will grow infinitely until the partition fills up.
The suggestion here is to use your operating system's standard log rotation tool, logrotate, and configure it to tell MySQL to switch to a new log file after the old one has been archived.
Another point worth mentioning here is that if you are not actively using the slow query log for performance tuning, you can try to disable it. On the other hand, MySQL can write the slow query log to a table (mysql.slow_log) instead of a file. This can be managed with standard SQL and does not consume disk space in the same way a flat file does, though it can still grow large. You can configure this via the log_output system variable.
Hope the above information is helpful!