Deprecate failureReason column of JSON query log. (#2364)

Deprecate failureReason and recommend to use errorInfo instead

---------

Co-authored-by: NataliaIvakina <[email protected]>
Co-authored-by: Reneta Popova <[email protected]>

Author: 3 people

modules/ROOT/pages/changes-deprecations-removals.adoc

@@ -57,6 +57,7 @@ It is highly recommended to keep it enabled and not to alter it. +
 If you require the _debug.log_ messages in a different format, create an additional Appender since the Neo4j Support team uses the default one.
 For more information, see xref:monitoring/logging.adoc#_default_logging_configuration[Default logging configuration].
 
+
 === Built-in procedures
 
 .See procedures removed in Neo4j 2025.01 without replacement.
@@ -517,6 +518,12 @@ Replaced by: xref:procedures.adoc#procedure_dbms_cluster_secondaryreplicationdis
 |===
 ====
 
+=== Logging
+
+Starting from 2025.05, the `failureReason` column of the JSON format query log is deprecated.
+Instead, use the `errorInfo` column.
+For details, refer to xref:monitoring/logging.adoc#_json_format_log_entries[Logging -> JSON format log entries for log type query].
+
 === Neo4j-admin tool
 
 .See all deprecated commands

modules/ROOT/pages/monitoring/logging.adoc

@@ -1285,9 +1285,10 @@ Included when xref:configuration/configuration-settings.adoc#config_db.logs.quer
 | annotationData
 | Metadata attached to the transaction.
 
-| failureReason
+| failureReason label:deprecated[Deprecated in 2025.05]
 | Reason for failure.
 Included when applicable.
+Replaced by `errorInfo`.
 
 | errorInfo
 | GQL error information as a JSON object.