Introduction to the Percona Server Audit Log feature

Percona has developed an Audit Log feature that is now included in Percona Server since the recent 5.5 and 5.6 releases. This implementation is alternative to the MySQL Enterprise Audit Log Plugin: Percona re-implemented the Audit Plugin code as GPL as Oracle’s code was closed source. This post is a quick introduction to this plugin.

There are two ways to install the Percona MySQL Audit Plugin:

or in my.cnf

Verify installation

Let’s see variables provided by the Percona MySQL Audit Plugin:

The Percona MySQL Audit Plugin can log using the memory buffer to deliver better performance. Messages will be written into memory buffer first and then flushed to file in background. A certain amount of events can be lost in case of server crash or power outage. Another option is to log directly to file without using memory buffer. There is also an option to fsync every event.

Set audit_log_strategy to control log flushing:

  • ASYNCHRONOUS log using memory buffer, do not drop events if buffer is full
  • PERFORMANCE log using memory buffer, drop events if buffer is full
  • SEMISYNCHRONOUS log directly to file, do not fsync every event
  • SYNCHRONOUS log directly to file, fsync every event

audit_log_buffer_size specifies the size of memory buffer, it makes sense only for ASYNCHRONOUS and PERFORMANCE strategy.

Variable audit_log_file specifies the file to log into. It’s value can be path relative to datadir or absolute path.

The Percona MySQL Audit Plugin can automatically rotate log file based on size. Set audit_log_rotate_size to enable this feature. File is rotated when log grew in size to specified amount of bytes. Set audit_log_rotations to limit the number of log files to keep.

It is possible to log only logins or only queries by setting audit_log_policy value.

Log file format
Lets see how audit records look like

OLD format (audit_log_format = OLD):

NEW format (audit_log_format = NEW):

The difference is that the audit record in the OLD format was written as a single element with attributes, while in the NEW format it is written as a single element with sub-elements.

A good idea of what each sub-element means can be found in Audit Plugin API documentation here:

Lets compare performance of different audit_log_strategy modes. I used readonly sysbench on my laptop for it. Workload is CPU-bound with dataset fit in buffer pool and I set number of sysbench threads to the amount for which count of transactions per seconds is maximum.

sysbench TPS for Percona Audit Log Plugin

I got TPS drop for PERFORMANCE and ASYNCHRONOUS strategies around 7%, 9% for SEMISYNCHRONOUS and 98% for SYNCHRONOUS which shows that syncing every logged statement to disk is not the best thing for performance.


Of course any software has bugs and this plugin has plenty of them. Please give it a try and provide us your feedback. Report any issues here:

Share this post

Comments (3)

  • Shlomi Noach

    Please consider adding both CSV and JSON formats.
    XML format is so eighties 🙂

    May 16, 2014 at 11:31 am
  • Denis

    Hello Guys, Thank you for the Great Article. Just friendly notice 🙂 , in this string “mysql> SHOW PLUGINSG” you did missed “/”, total it should be “mysql> SHOW PLUGINS\G”. Just for people, who will follow this tutorial.

    June 11, 2014 at 9:49 am
  • Franck Leveneur

    Would it be possible to filter like MacAfee plugin:
    1- mysql account: audit_whitelist_users
    2- sql command: audit_record_cmds

    These 2 filters would avoid login un-necessary App sql accountsand focus on only important sql commands (Alter,Create,Insert,Update,Delete),

    June 18, 2014 at 7:54 pm

Comments are closed.

Use Percona's Technical Forum to ask any follow-up questions on this blog topic.