mountPath: /var/log/tidb name: slowlog baseImage: /tidb-ent:v5.4.0 plugins: - audit-1 Use TiUP to deploy the plugin Add the plugin to an existing cluster 1. Create a file plugin status You can view the current plugin loading and enabling status by running the `show plugins` command in MySQL: ● Name: plugin name ● Status: plugin status, including the loading status command: mysql> admin plugins enable audit; If you do not need to audit the CONNECTION and GENERAL events, run the following command to disable the audit: mysql> admin plugins disable audit; © 2022

set global tidb_audit_enabled = 1; set global tidb_audit_enabled = 0; admin plugins enable audit; admin plugins disable audit; The number of audit event classes for one SQL statement One or more using audit_log_create_rule Modify the table mysql.tidb_audit_table_acc ess, then run flush tidb plugins audit to refresh the configuration Filter the Wildcards with JSON Regular expressions © 2023 PingCAP completed and verified, execute the following command to disable the legacy audit plugin: mysql> admin plugins disable audit; © 2023 PingCAP. All Rights Reserved. 20

variables, auto-analyze is triggered only during this time period. • The default storage directory for plugins is changed from "" to /data/deploy/plugin. • The DM code is migrated to the folder “dm” in TiCDC file: cd grafana-6.1.6 && vi conf/grafana.ini ... [paths] data = ./data logs = ./data/log plugins = ./data/plugins [server] http_port = 3000 domain = 192.168.199.113 [database] [session] [analytics] check_for_updates directory to load plugins as specified by a command-line flag. 1377 12.4.1.39 plugin_load • Scope: INSTANCE • Default value: “” • Indicates the plugins to load when TiDB is started. These plugins are specified

BACKUP_ADMIN – RESTORE_ADMIN – ROLE_ADMIN – CONNECTION_ADMIN – SYSTEM_VARIABLES_ADMIN You can also use plugins to add new privileges. To check out all supported privileges, execute the SHOW PRIVILEGES statement file: cd grafana-6.1.6 && vi conf/grafana.ini ... [paths] data = ./data logs = ./data/log plugins = ./data/plugins [server] http_port = 3000 domain = 192.168.199.113 [database] [session] [analytics] check_for_updates 12.7.1.26 --plugin-dir • The storage directory for plugins. • Default: “/data/deploy/plugin” 12.7.1.27 --plugin-load • The names of the plugins to be loaded, each separated by a comma. • Default: “”

file: cd grafana-6.1.6 && vi conf/grafana.ini ... [paths] data = ./data logs = ./data/log plugins = ./data/plugins [server] http_port = 3000 domain = 192.168.199.113 [database] [session] [analytics] check_for_updates directory to load plugins as specified by a command-line flag. 12.4.1.36 plugin_load • Scope: INSTANCE • Default value: “” • Indicates the plugins to load when TiDB is started. These plugins are specified 12.7.1.26 --plugin-dir • The storage directory for plugins. • Default: “/data/deploy/plugin” 12.7.1.27 --plugin-load • The names of the plugins to be loaded, each separated by a comma. • Default: “”

cd grafana-7.5.11 && vi conf/grafana.ini ... [paths] data = ./data logs = ./data/log plugins = ./data/plugins [server] http_port = 3000 domain = 192.168.199.113 [database] [session] [analytics] check_for_updates directory to load plugins as specified by a command-line flag. 1949 12.4.1.39 plugin_load • Scope: INSTANCE • Default value: “” • Indicates the plugins to load when TiDB is started. These plugins are specified 12.7.1.26 --plugin-dir • The storage directory for plugins. • Default: "/data/deploy/plugin" 12.7.1.27 --plugin-load • The names of the plugins to be loaded, each separated by a comma. • Default: ""

d> 5.0.1 <plugins> 472 org.apache.maven.plugins maven-assembly-plugin 3.3.0 package single plugins> Coding Then write the code: package com.pingcap.txn; import com.zaxxer upgrade, loading certain plugins that require executing DDL statements might cause the upgrade to get stuck. Solution: avoid loading plugins during the upgrade. Instead, load plugins only after the upgrade

d> 5.0.1 <plugins> 459 org.apache.maven.plugins maven-assembly-plugin 3.3.0 package single plugins> Coding Then write the code: package com.pingcap.txn; import com.zaxxer upgrade, loading certain plugins that require executing DDL statements might cause the upgrade to get stuck. Solution: avoid loading plugins during the upgrade. Instead, load plugins only after the upgrade

<plugins> org.springframework.boot spring-boot-maven-plugin plugins> 181 User tId> 5.0.1 <plugins> org.apache.maven.plugins maven-assembly-plugin 3.3.0 package single plugins> 390 Coding Then write the code: package com.pingcap.txn; import com.zaxxer

d> 5.0.1 <plugins> 487 org.apache.maven.plugins maven-assembly-plugin 3.3.0 package single plugins> Coding Then write the code: package com.pingcap.txn; import com.zaxxer upgrade, loading certain plugins that require executing DDL statements might cause the upgrade to get stuck. Solution: avoid loading plugins during the upgrade. Instead, load plugins only after the upgrade