MySQL Workbench Manual  /  Administrative Tasks  /  MySQL Audit Inspector Interface

6.6 MySQL Audit Inspector Interface

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:

Figure 6.25 Workbench: Audit Inspector: Initializing

Content is described in the surrounding text.


Generating the cache file can take a long time. If you press Abort during the caching process, MySQL Workbench will save the results that were cached at the point you pressed Abort.

After caching an audit log, the Audit Inspector page will display the results as shown in the following figure:

Figure 6.26 Workbench: Audit Inspector

Content is described in the surrounding text.

The search field offers criteria for narrowing the displayed events, including Show events of type Fetch and Show events of type Query, and defaults to Show all events. Custom filters are also available.

You can Add Files to Cache from the main Audit Inspector page. The following figure shows an example file to add:

Figure 6.27 Workbench: Audit Inspector: Add Files to Cache

Content is described in the surrounding text.

Future uses of the Audit Inspector will require the password that you set during the initial step. The next figure shows that the audit log cache is locked:

Figure 6.28 Workbench: Audit Inspector: Unlock

Content is described in the surrounding text.

User Comments
Sign Up Login You must be logged in to post a comment.