MySQL Workbench offers a GUI interface to the Audit Inspector.
Initially, when you first load the Audit Inspector, you must use MySQL Workbench to cache the audit log for performance reasons. MySQL Workbench will then parse, index, and retrieve values from the encrypted cached file on your local computer.
MySQL Workbench will prompt for sudo access if the MySQL Workbench user is unable to read the audit log file.
At this stage, you also set a password for the encrypted file that will be used when viewing this file. The initial screen looks similar to the figure that follows:
Generating the cache file can take a long time. If you pressduring the caching process, MySQL Workbench will save the results that were cached at the point you pressed .
After caching an audit log, the Audit Inspector page will display the results as shown in the following figure:
The search field offers criteria for narrowing the displayed events, includingand , and defaults to . Custom filters are also available.
You canfrom the main Audit Inspector page. The following figure shows an example file to add:
Future uses of thewill require the password that you set during the initial step. The next figure shows that the audit log cache is locked: