Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion modules/ROOT/pages/configuration/configuration-settings.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -1699,7 +1699,7 @@ m|+++true+++
|Description
a|The load balancing plugin to use.
|Valid values
a|A string that specified load balancer plugin exist..
a|A string.
|Default value
m|+++server_policies+++
|===
Expand Down Expand Up @@ -2457,6 +2457,10 @@ a|A boolean.
m|+++false+++
|===

[NOTE]
====
Keep in mind that if Neo4j receives a malformed query that cannot be parsed, it cannot obfuscate its literals (because it does not know which parts are literals) and, therefore, the query text will not be included in any logging.
====

[role=label--dynamic]
[[config_db.logs.query.parameter_logging_enabled]]
Expand Down
4 changes: 3 additions & 1 deletion modules/ROOT/pages/monitoring/logging.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -875,8 +875,10 @@ This is useful when Cypher queries expose sensitive information.
====
Node labels, relationship types, and map property keys are still shown.
Changing the setting does not affect cached queries.
Therefore, if you want the switch to have an immediate effect, you must also clear the query cache; `CALL db.clearQueryCaches()`.
Therefore, if you want the switch to have an immediate effect, you must also clear the query cache; `CALL db.clearQueryCaches()`. +
Also, keep in mind that if Neo4j receives a malformed query that cannot be parsed, it cannot obfuscate its literals (because it does not know which parts are literals) and, therefore, the query text will not be included in any logging.
====

[WARNING]
====
This does not obfuscate literals in parameters.
Expand Down