You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -4,7 +4,7 @@ The Audit Log Filter component allows you to monitor, log, and block a connectio
4
4
5
5
Enabling the component produces a log file that contains a record of server activity. The log file has information on connections and databases accessed by that connection.
6
6
7
-
The component uses the `mysql` system database to store filter and user account data. Set the [`audit_log_filter.database`](audit-log-filter-variables.md#audit_log_filter.database) variable at server startup to select a different database.
7
+
The component uses the `mysql` system database to store filter and user account data. Set the [`audit_log_filter.database`](audit-log-filter-variables.md#audit_log_filterdatabase) variable at server startup to select a different database.
8
8
9
9
The `AUDIT_ADMIN` privilege is required to enable users to manage the Audit Log Filter component.
10
10
@@ -26,106 +26,15 @@ The Audit Log Filter component uses `mysql` system database tables in the `InnoD
26
26
27
27
The `audit_log_filter` table stores the definitions of the filters and has the following column definitions:
@@ -576,7 +575,7 @@ The default value is 0 (zero). This value disables the expiration of passwords.
576
575
577
576
If the component starts and encryption is enabled, the component checks for an audit log filter encryption password. If a password is not found, the component generates a random password.
578
577
579
-
Call [`audit_log_filter_encryption_set()`](#audit_log_filter_encryption_set) to set a specific password.
578
+
Call [audit_log_encryption_password_set(new_password)](#audit_log_encryption_password_setnew_password) to set a specific password.
580
579
581
580
582
581
### `audit_log_filter.prune_seconds`
@@ -600,8 +599,8 @@ A value greater than 0 enables pruning. An audit log filter file can be pruned a
600
599
601
600
To enable log pruning, you must set one of the following:
602
601
603
-
* Enable log rotation by setting [`audit_log_filter.rotate_on_size`](audit_log_filterrotate_on_size)
604
-
* Add a value greater than 0 (zero) for either [`audit_log_filter.max_size`](audit_log_filtermax_size) or [`audit_log_filter.prune_seconds`](audit_log_filterprune_seconds)
602
+
* Enable log rotation by setting [`audit_log_filter.rotate_on_size`](#audit_log_filterrotate_on_size)
603
+
* Add a value greater than 0 (zero) for either [`audit_log_filter.max_size`](#audit_log_filtermax_size) or [`audit_log_filter.prune_seconds`](#audit_log_filterprune_seconds)
605
604
606
605
607
606
### `audit_log_filter.read_buffer_size`
@@ -617,7 +616,7 @@ To enable log pruning, you must set one of the following:
617
616
618
617
This option is only supported for JSON-format files.
619
618
620
-
The size of the buffer for reading from the audit log filter file. The [`audit_log_filter_read()`](audit_log_filter_read) reads only from this buffer size.
619
+
The size of the buffer for reading from the audit log filter file. The `audit_log_filter_read()` reads only from this buffer size.
621
620
622
621
### `audit_log_filter.rotate_on_size`
623
622
@@ -672,7 +671,7 @@ Defines the Audit Log filter component's logging method. The valid values are th
672
671
| Data type | String |
673
672
| Default | LOG_USER |
674
673
675
-
Specifies the syslog `facility` value. The option has the same meaning as the appropriate parameter described in the [syslog(3) manual](https://linux.die.net/man/3/syslog).
674
+
Specifies the syslog `facility` value. The option has the same meaning as the appropriate parameter described in the [syslog(3) manual](https://man7.org/linux/man-pages/man3/syslog.3.html).
676
675
677
676
678
677
### `audit_log_filter.syslog_priority`
@@ -685,7 +684,7 @@ Specifies the syslog `facility` value. The option has the same meaning as the ap
685
684
| Data type | String |
686
685
| Default | LOG_INFO |
687
686
688
-
Defines the `priority` value for the syslog. The option has the same meaning as the appropriate parameter described in the [syslog(3) manual](https://linux.die.net/man/3/syslog).
687
+
Defines the `priority` value for the syslog. The option has the same meaning as the appropriate parameter described in the [syslog(3) manual](https://man7.org/linux/man-pages/man3/syslog.3.html).
|[`dictionaries_flush_interval_seconds (integer, unsigned)`](#dictionaries_flush_interval_secondsinteger-unsigned)| The number of seconds between updates to the internal dictionary cache to match changes in the dictionaries table.|
966
-
|[`masking_database(str)`](#masking_databasestr)| Set a different database name to use for the dictionaries table. |
966
+
|[`masking_database(string)`](#masking_databasestring)| Set a different database name to use for the dictionaries table. |
Copy file name to clipboardExpand all lines: docs/data-masking-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ To fix this, you can use the new [`masking_dictionaries_flush()`](data-masking-f
39
39
40
40
The changes also affect how row-based replication works. When dictionary changes happen on the source server, they travel through the binary log to the replica server. While the replica applies these changes to its table correctly, the dictionary term cache doesn't update right away.
41
41
42
-
To handle this, there's a new component system variable called [`component_masking_functions.dictionaries_flush_interval_seconds()`](data-masking-function-list.html#dictionaries_flush_interval_secondsinteger-unsigned)
42
+
To handle this, there's a new component system variable called [`component_masking_functions.dictionaries_flush_interval_seconds()`](data-masking-function-list.md#dictionaries_flush_interval_secondsinteger-unsigned)
43
43
44
44
By default, it's set to 0. When you set it higher, the system starts a background process that refreshes the cache at your specified interval. This helps replicas stay in sync after receiving binary log updates. The value specifies the number of seconds between each sync.
Copy file name to clipboardExpand all lines: docs/index-info-schema-tables.md
+10-15Lines changed: 10 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,30 +2,25 @@
2
2
3
3
This is a list of the `INFORMATION_SCHEMA TABLES` that exist in Percona Server for MySQL with XtraDB. The entry for each table points to the page in the documentation where it’s described.
Copy file name to clipboardExpand all lines: docs/manage-audit-log-filter.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ If automatic rotation is enabled, you can prune the log file. This pruning opera
11
11
12
12
## Manual log rotation
13
13
14
-
The default setting for [`audit_log_filter.rotate_on_size`](audit-log-filter-variables.md#audit_log_filter_rotate_on_size) is 1GB. If this option is set to `0`, the audit log filter component does not do an automatic rotation of the log file. You must do the rotation manually with this setting.
14
+
The default setting for [`audit_log_filter.rotate_on_size`](audit-log-filter-variables.md#audit_log_filterrotate_on_size) is 1GB. If this option is set to `0`, the audit log filter component does not do an automatic rotation of the log file. You must do the rotation manually with this setting.
15
15
16
16
The `SELECT audit_log_rotate()` command renames the file and creates a new audit log filter file with the original name. You must have the `AUDIT_ADMIN` privilege.
0 commit comments