MySQL Enterprise Audit • Audit_log_current_size • Audit_log_event_max_drop_size • Audit_log_events • Audit_log_events_filtered • Audit_log_events_lost • Audit_log_events_written • Audit_log_total_size • Audit_log_write_waits •Only SQL statements are logged. Changes made by no-SQL APIs, such as memcached, Node.JS, and the NDB API, are not logged. •Only top-level statements are logged, not statements within stored programs such as triggers or stored procedures. •Contents of files referenced by statements such as  LOAD DATA  are not logged. •All changes to be logged must be done using the SQL interface. Changes using no-SQL interfaces, such as those provided by the NDB API, memcached, or ClusterJ, are not logged. 1541 NDB Cluster.   It is possible to use MySQL Enterprise Audit with MySQL NDB Cluster, subject to the following conditions: MySQL Enterprise Audit is subject to these general restrictions: The number of times an event had to wait for space in the audit log buffer in asynchronous logging mode. For a description of logging modes, see Section 6.4.5.5, “Configuring Audit Logging Characteristics” . The total size of events written to all audit log files. Unlike  Audit_log_current_size , the value of Audit_log_total_size  increases even when the log is rotated. The number of events written to the audit log. The number of events lost in performance logging mode because an event was larger than the available audit log buffer space. This value may be useful for assessing how to set  audit_log_buffer_size to size the buffer for performance mode. For a description of logging modes, see Section 6.4.5.5, “Configuring Audit Logging Characteristics” . The number of events handled by the audit log plugin that were filtered (not written to the log) based on filtering policy (see Section 6.4.5.5, “Configuring Audit Logging Characteristics” ). The number of events handled by the audit log plugin, whether or not they were written to the log based on filtering policy (see Section 6.4.5.5, “Configuring Audit Logging Characteristics” ). The size of the largest dropped event in performance logging mode. For a description of logging modes, see Section 6.4.5.5, “Configuring Audit Logging Characteristics” . The size of the current audit log file. The value increases when an event is written to the log and is reset to 0 when the log is rotated. 6.4.5.11 Audit Log Restrictions