hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added logging of matching and non-matching queries to dbfwfilter

Browse Source 
When configured to log matching queries, the dbfwfilter will log all queries
that match a rule. The rule name, user name and the query itself are logged.

It is also possible to match all queries that do not match a rule. Only the user
name and query is logged in this mode.
This commit is contained in:
Markus Makela
2016-01-29 21:48:29 +02:00
parent 5efd5d8927
commit 6055ba25bf
2 changed files with 108 additions and 96 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/Filters/Database-Firewall-Filter.md
View File

@ -36,6 +36,18 @@ The database firewall filter has one mandatory parameter that defines the locati
This parameter is optional and determines what action is taken when a query matches a rule. The value can be either `allow`, which allows all matching queries to proceed but blocks those that don't match, or `block`, which blocks all matching queries, or `ignore` which allows all queries to proceed.
#### `log_match`
Log all queries that match a rule. For the `any` matching mode, the name of
the rule that matched is logged and for other matching modes, the name of
the last matching rule is logged. In addition to the rule name the matched
user and the query itself is logged. The log messages are logged at the notice level.
#### `log_no_match`
Log all queries that do not match a rule. The matched user and the query is
logged. The log messages are logged at the notice level.
## Rule syntax
The rules are defined by using the following syntax: