MySQL Enterprise Audit Introduced 8.0.26 System Variable audit_log_max_size Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 0 Minimum Value 0 Maximum Value (Windows) 4294967295 Maximum Value (Other) 18446744073709551615 Unit bytes Block Size 4096 audit_log_max_size  pertains to audit log file pruning, which is supported for JSON-format log files only. It controls pruning based on combined log file size: •A value of 0 (the default) disables size-based pruning. No size limit is enforced. •A value greater than 0 enables size-based pruning. The value is the combined size above which audit log files become subject to pruning. If you set  audit_log_max_size  to a value that is not a multiple of 4096, it is truncated to the nearest multiple. In particular, setting it to a value less than 4096 sets it to 0 and no size-based pruning occurs. If both  audit_log_max_size  and  audit_log_rotate_on_size  are greater than 0, audit_log_max_size  should be more than 7 times the value of  audit_log_rotate_on_size . Otherwise, a warning is written to the server error log because in this case the “granularity”  of size-based pruning may be insufficient to prevent removal of all or most rotated log files each time it occurs. Note Setting  audit_log_max_size  by itself is not sufficient to cause log file pruning to occur because the pruning algorithm uses  audit_log_rotate_on_size , audit_log_max_size , and  audit_log_prune_seconds  in conjunction. For details, see Space Management of Audit Log Files. • audit_log_password_history_keep_days 1535 Command-Line Format --audit-log-password-history-keep- days=# Introduced 8.0.17 System Variable audit_log_password_history_keep_days Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 0