mysql.binlog.disk_use

Sudden spike in binary log disk usage triggers CPU, network, and IOPS saturation, creating a cascading slowdown. Large write operations (bulk updates, schema changes) generate excessive binlog data faster than it can be purged, leading to storage pressure and performance degradation.

Storage fills up due to binary log retention exceeding available disk space. Binary logs accumulate faster than they are purged, often during replication lag or when binlog_expire_logs_seconds is set too high, leading to storage exhaustion.