Storage Full from Binary Log Accumulation
criticalStorage 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.
mysql.binlog.disk_use consuming >70% of available storage, binlog_files count continuously increasing, with mysql.replication.replicas_connected > 0 and mysql.replication.seconds_behind_source > 3600
Check binlog_expire_logs_seconds configuration. Verify all replicas have read required binlogs by checking mysql.replication.seconds_behind_source on each replica. If replication is healthy, manually purge old binlogs using PURGE BINARY LOGS TO or PURGE BINARY LOGS BEFORE. Increase storage allocation if binlog retention is required for recovery/compliance. Set up alerting on mysql.binlog.disk_use growth rate. Consider setting binlog_space_limit (MySQL 8.0.33+) to prevent runaway growth.