> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/maxscale/reference/maxscale-filters/maxscale-query-log-all-filter.md).

# MaxScale Query Log All Filter

Log every SQL query passing through MaxScale. This filter provides comprehensive audit trails by recording query text, execution time, and client details.

## Overview

The Query Log All (QLA) filter logs query content. Logs are written to a file in CSV format. Log elements are configurable and include the time submitted and the SQL statement text, among others.

## Configuration

A minimal configuration is below.

```
[MyLogFilter]
type=filter
module=qlafilter
filebase=/tmp/SqlQueryLog

[MyService]
type=service
router=readconnroute
servers=server1
user=myuser
password=mypasswd
filters=MyLogFilter
```

## Log Rotation

The `qlafilter` logs can be rotated by executing the `maxctrl rotate logs` command. This will cause the log files to be reopened when the next message is written to the file. This applies to both unified and session type logging.

## Settings

The QLA filter has one mandatory parameter, `filebase`, and a number of optional parameters. These were introduced in the 1.0 release of MariaDB MaxScale.

### `filebase`

* Type: string
* Mandatory: Yes
* Dynamic: No
* Description: Specifies the base filename for session log files with unique session identifiers appended to create individual output files.

The basename of the output file created for each session. A session index is added to the filename for each written session file. For unified log files,*.unified* is appended.

```
filebase=/tmp/SqlQueryLog
```

### `match`

* Type: [regex](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#regular-expressions)
* Mandatory: No
* Dynamic: Yes
* Default: None
* Description: Specifies a regex pattern for queries ti include and process by the filter.

Include queries that match the regex.

### `exclude`

* Type: [regex](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#regular-expressions)
* Mandatory: No
* Dynamic: Yes
* Default: None
* Description: Defines a regex pattern to exclude queries from matching and filtering.

Exclude queries that match the regex.

### `options`

* Type: [enum\_mask](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#enumerations)
* Mandatory: No
* Dynamic: Yes
* Values: `case`, `ignorecase`, `extended`
* Default: `case`
* Description: Defines the regex matching behavior (case sensitivity and extended syntax) for filter queries.

The `extended` option enables PCRE2 extended regular expressions.

### `user`

* Type: string
* Mandatory: No
* Dynamic: Yes
* Default: `""`
* Description: Limits logging to sessions initiated by a specific username.

Limit logging to sessions with this user.

### `source`

* Type: string
* Mandatory: No
* Dynamic: Yes
* Default: `""`
* Description: Limits logging to sessions that originate from specific client source addresses.

Limit logging to sessions with this client source address.

### `user_match`

* Type: [regex](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#regular-expressions)
* Mandatory: No
* Dynamic: Yes
* Description: Specifies a regex pattern to include queries only from specific users for logging.

Only log queries from users that match this pattern. If the `user` parameter is used, the value of `user_match` is ignored.

Here is an example pattern that matches the users `alice` and `bob`:

```
user_match=/(^alice$)|(^bob$)/
```

### `user_exclude`

* Type: [regex](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#regular-expressions)
* Mandatory: No
* Dynamic: Yes
* Description: Defines a regex pattern that prevent requests from specific users from being logged.

Exclude all queries from users that match this pattern. If the `user` parameter is used, the value of `user_exclude` is ignored.

Here is an example pattern that excludes the users `alice` and `bob`:

```
user_exclude=/(^alice$)|(^bob$)/
```

### `source_match`

* Type: [regex](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#regular-expressions)
* Mandatory: No
* Dynamic: Yes
* Description: Defines a regex pattern to include only queries from specific client IP addresses or hosts from logging.

Only log queries from hosts that match this pattern. If the `source` parameter is used, the value of `source_match` is ignored.

Here is an example pattern that matches the loopback interface as well as the address `192.168.0.109`:

```
source_match=/(^127[.]0[.]0[.]1)|(^192[.]168[.]0[.]109)/
```

### `source_exclude`

* Type: [regex](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#regular-expressions)
* Mandatory: No
* Dynamic: Yes
* Description: Defines a regex pattern for excluding requests from specified client IP addresses or hosts from logging.

Exclude all queries from hosts that match this pattern. If the `source` parameter is used, the value of `source_exclude` is ignored.

Here is an example pattern that excludes the loopback interface as well as the address `192.168.0.109`:

```
source_exclude=/(^127[.]0[.]0[.]1)|(^192[.]168[.]0[.]109)/
```

### `log_type`

* Type: [enum\_mask](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#enumerations)
* Mandatory: No
* Dynamic: Yes
* Values: `session`, `unified`, `stdout`
* Default: `session`
* Description: Defines the logging output type, such as per-session files, a unified log file, or standard output.

The type of log file to use.

| Value   | Description                     |
| ------- | ------------------------------- |
| session | Write to session-specific files |
| unified | Use one file for all sessions   |
| stdout  | Same as unified, but to stdout  |

### `log_data`

* Type: [enum\_mask](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#enumerations)
* Mandatory: No
* Dynamic: Yes
* Values: `service`, `session`, `date`, `user`, `reply_time`, `total_reply_time`, `query`, `default_db`, `num_rows`, `reply_size`, `transaction`, `transaction_time`, `num_warnings`, `error_msg`
* Default: `date, user, query`
* Description: Specifies the fields, such as query details, user, timing, and execution metadata, that are present in each log entry.

Type of data to log in the log files.

| Value              | Description                                             |
| ------------------ | ------------------------------------------------------- |
| service            | Service name                                            |
| session            | Unique session id (ignored for session files)           |
| date               | Timestamp                                               |
| user               | User and hostname of client                             |
| reply\_time        | Duration from client query to first server reply        |
| total\_reply\_time | Duration from client query to last server reply (v6.2)  |
| query              | The SQL of the query if it contains it                  |
| default\_db        | The default (current) database                          |
| num\_rows          | Number of rows in the result set (v6.2)                 |
| reply\_size        | Number of bytes received from the server (v6.2)         |
| transaction        | BEGIN, COMMIT and ROLLBACK (v6.2)                       |
| transaction\_time  | The duration of a transaction (v6.2)                    |
| num\_warnings      | Number of warnings in the server reply (v6.2)           |
| error\_msg         | Error message from the server (if any) (v6.2)           |
| server             | The server where the query was routed (if any) (v22.08) |
| command            | The protocol command that was executed (v24.02)         |

The durations *reply\_time* and *total\_reply\_time* are by default in milliseconds, but can be specified to another unit using *duration\_unit*.

The log entry is written when the last reply from the server is received. Prior to version 6.2 the entry was written when the query was received from the client, or if *reply\_time* was specified, on first reply from the server.

**NOTE** The *error\_msg* is the raw message from the server. Even if *use\_canonical\_form* is set the error message may contain user defined constants. For example:

```
MariaDB [test]> select secret from T where x password="clear text pwd";
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
that corresponds to your MariaDB server version for the right syntax to
use near 'password="clear text pwd"' at line 1
```

Starting with MaxScale 24.02, the `query` parameter now correctly logs the execution of binary protocol commands as SQL ([MXS-4959](https://jira.mariadb.org/browse/MXS-4959)). The execution of batched statements (COM\_STMT\_BULK\_LOAD) used by some connectors is not logged.

### `duration_unit`

* Type: string
* Mandatory: No
* Dynamic: Yes
* Default: `milliseconds`
* Description: Defines the time unit used for logging durations.

The unit for logging a duration. The unit can be `milliseconds` or `microseconds`. The abbreviations `ms` for milliseconds and `us` for microseconds are also valid. This option is available as of MaxScale version 6.2.

### `use_canonical_form`

* Type: [bool](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#booleans)
* Mandatory: No
* Dynamic: Yes
* Default: `false`
* Description: Log queries in canonical format, replacing user-defined constants with placeholders to ensure consistent and secure output.

When this option is true the canonical form of the query is logged. In the canonical form all user defined constants are replaced with question marks. This option is available as of MaxScale version 6.2.

### `flush`

* Type: [bool](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#booleans)
* Mandatory: No
* Dynamic: Yes
* Default: `false`
* Description: Manages whether log files are immediately flushed to disk after each write operation.

Flush log files after every write.

### `append`

* Type: [bool](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#booleans)
* Mandatory: No
* Dynamic: Yes
* Default: `true`
* Description: Defines whether a new routing hint is added to existing ones or replaces them when applied to matching queries.

### `separator`

* Type: string
* Mandatory: No
* Dynamic: Yes
* Default: `","`
* Description: Specifies the string used to separate fields within each log entry.

Defines the separator string between elements of log entries. The value should be enclosed in quotes.

### `newline_replacement`

* Type: string
* Mandatory: No
* Dynamic: Yes
* Default: `" "`
* Description: Specifies the string that is used to substitute newline characters in logged queries so that the log output is consistent and readable.

Default value is `" "` (one space). SQL-queries may include line breaks, which, if printed directly to the log, may break automatic parsing. This parameter defines what should be written in the place of a newline sequence (\r, \n or \r\n). If this is set as the empty string, then newlines are not replaced and printed as is to the output. The value should be enclosed in quotes.

```
newline_replacement=" NL "
```

## Limitations

* Trailing parts of SQL queries that are larger than 16MiB are not logged. This means that the log output might contain truncated SQL.
* Batched execution using COM\_STMT\_BULK\_EXECUTE is not converted into their textual form. This is done due to the large volumes of data that are usually involved with batched execution.

## Examples

### Example 1 - Query without primary key

Imagine you have observed an issue with a particular table and you want to determine if there are queries that are accessing that table but not using the primary key of the table. Let's assume the table name is PRODUCTS and the primary key is called PRODUCT\_ID. Add a filter with the following definition:

```
[ProductsSelectLogger]
type=filter
module=qlafilter
match=SELECT.*from.*PRODUCTS .*
exclude=WHERE.*PRODUCT_ID.*
filebase=/var/logs/qla/SelectProducts

[Product-Service]
type=service
router=readconnroute
servers=server1
user=myuser
password=mypasswd
filters=ProductsSelectLogger
```

The result of using this filter with the service used by the application would be a log file of all select queries querying PRODUCTS without using the PRODUCT\_ID primary key in the predicates of the query. Executing `SELECT * FROM PRODUCTS` would log the following into `/var/logs/qla/SelectProducts`:

```
07:12:56.324 7/01/2016, SELECT * FROM PRODUCTS
```

<sub>*This page is licensed: CC BY-SA / Gnu FDL*</sub>

{% @marketo/form formId="4316" %}