Rechercher dans le manuel MySQL
6.4.5.2 Installing or Uninstalling MySQL Enterprise Audit
This section describes how to install or uninstall MySQL Enterprise Audit, which is implemented using the audit log plugin and related components described in Section 6.4.5.1, “Audit Log Components”. For general information about installing plugins, see Section 5.6.1, “Installing and Uninstalling Plugins”.
Read this entire section before following its instructions. Parts of the procedure differ depending on your environment.
If installed, the audit_log
plugin involves
some minimal overhead even when disabled. To avoid this
overhead, do not install MySQL Enterprise Audit unless you plan to use it.
To be usable by the server, the plugin library file must be
located in the MySQL plugin directory (the directory named by
the plugin_dir
system
variable). If necessary, configure the plugin directory location
by setting the value of
plugin_dir
at server startup.
To install MySQL Enterprise Audit, look in the share
directory of your MySQL installation and choose the script that
is appropriate for your platform. The available scripts differ
in the suffix used to refer to the plugin library file:
audit_log_filter_win_install.sql
: Choose this script for Windows systems that use.dll
as the file name suffix.audit_log_filter_linux_install.sql
: Choose this script for Linux and similar systems that use.so
as the file name suffix.
Run the script as follows. The example here uses the Linux installation script. Make the appropriate substitution for your system.
shell> mysql -u root -p < audit_log_filter_linux_install.sql
Enter password: (enter root password here)
Some MySQL versions have introduced changes to the structure of the MySQL Enterprise Audit tables. To ensure that your tables are up to date for upgrades from earlier versions of MySQL 8.0, perform the MySQL upgrade procedure, making sure to use the option that forces an update (see Section 2.11, “Upgrading MySQL”). If you prefer to run the update statements only for the MySQL Enterprise Audit tables, see the following discussion.
As of MySQL 8.0.12, for new MySQL installations, the
USER
and HOST
columns in
the audit_log_user
table used by MySQL Enterprise Audit
have definitions that better correspond to the definitions of
the User
and Host
columns in the mysql.user
system table. For
upgrades to an installation for which MySQL Enterprise Audit is already
installed, it is recommended that you alter the table
definitions as follows:
To use MySQL Enterprise Audit in the context of master/slave replication,
Group Replication, or InnoDB cluster, you must prepare the
slave or secondary nodes prior to running the installation
script on the master or primary node. This is necessary
because the INSTALL PLUGIN
statement in the script is not replicated.
On each slave or secondary node, extract the
INSTALL PLUGIN
statement from the installation script and execute it manually.On the master or primary node, run the installation script as described previously.
To verify plugin installation, examine the
INFORMATION_SCHEMA.PLUGINS
table or
use the SHOW PLUGINS
statement
(see Section 5.6.2, “Obtaining Server Plugin Information”). For
example:
- FROM INFORMATION_SCHEMA.PLUGINS
- +-------------+---------------+
- | PLUGIN_NAME | PLUGIN_STATUS |
- +-------------+---------------+
- | audit_log | ACTIVE |
- +-------------+---------------+
If the plugin fails to initialize, check the server error log for diagnostic messages.
After MySQL Enterprise Audit is installed, you can use the
--audit-log
option for subsequent server
startups to control audit_log
plugin
activation. For example, to prevent the plugin from being
removed at runtime, use this option:
[mysqld]
audit-log=FORCE_PLUS_PERMANENT
If it is desired to prevent the server from running without the
audit plugin, use --audit-log
with a value of FORCE
or
FORCE_PLUS_PERMANENT
to force server startup
to fail if the plugin does not initialize successfully.
By default, rule-based audit log filtering logs no auditable events for any users. This differs from legacy audit log behavior, which logs all auditable events for all users (see Section 6.4.5.8, “Legacy Mode Audit Log Filtering”). Should you wish to produce log-everything behavior with rule-based filtering, create a simple filter to enable logging and assign it to the default account:
The filter assigned to %
is used for
connections from any account that has no explicitly assigned
filter (which initially is true for all accounts).
Once installed as just described, MySQL Enterprise Audit remains installed until uninstalled. To remove it, execute the following statements:
- UNINSTALL PLUGIN audit_log;
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-audit-log-installation.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.