Update the changelog page #415
Conversation
| | 03N85 | ||
| | Neo.ClientNotification.Cluster.ServerCaughtUp | ||
| * A new JSON template is available for the query log, which is the default set in _server_log.xml_. | ||
| It contains the `errorInfo` entry, but not the `failureReason` entry, which is switched off by default. |
There was a problem hiding this comment.
Should we add a link to the Ops manual here -- https://neo4j.com/docs/operations-manual/current/monitoring/logging/#_json_format_log_entries?
There was a problem hiding this comment.
Yeah, it makes sense, but maybe to here: https://neo4j.com/docs/operations-manual/current/monitoring/logging/#gql-error-information.
There was a problem hiding this comment.
Yeah, it makes sense, but maybe to here: https://neo4j.com/docs/operations-manual/current/monitoring/logging/#gql-error-information.
True! Much better
There was a problem hiding this comment.
Actually, the new thing here is the new JSON template, which is the default set in server_logs.xml. The other information is not so important. errorInfo is introduced in 5.25 and failureReason entry is deprecated in 2025.05..
There was a problem hiding this comment.
In other words, I am not sure where to link to.
renetapopova
force-pushed
the
dev-changelog
branch
from
28709f2 to
aa823d8
Compare
| | 03N85 | ||
| | Neo.ClientNotification.Cluster.ServerCaughtUp | ||
| * A new JSON template is available for the query log, which is the default set in _server_logs.xml_. | ||
| It contains the `errorInfo` entry, but not the `failureReason` entry, which is switched off by default. |
There was a problem hiding this comment.
| It contains the `errorInfo` entry, but not the `failureReason` entry, which is switched off by default. | |
| It contains the `errorInfo` entry, but not the `failureReason` entry, which is switched off by default starting from 2025.05. | |
| For more details about the JSON template for the query log, refer to the link:https://neo4j.com/docs/operations-manual/current/monitoring/logging/#_json_format_log_entries[Operations manual -> Monitoring -> Logging]. | |
| To learn more about the JSON object `errorInfo` in the query log, visit the link:https://neo4j.com/docs/operations-manual/current/monitoring/logging/#gql-error-information[Operations manual -> Logging -> GQL error information]. |
There was a problem hiding this comment.
Ideally, it would be to link to the table Table 10. JSON format log entries for log type query.
But I still think it's enough to link to the JSON format log entries because we talk about the changes made to the JSON template.
GQL error information is part of JSON format log entries but it has the same 4th level which is understandable. It would be too much to place it on the 5th level.
We can add a line here speaking about the GQL error specifically
| |=== | ||
| | GQLSTATUS | ||
| | Neo4j code | ||
| = Changes and deprecations |
There was a problem hiding this comment.
actually, now I'm starting thinking that we should place the information about the deprecated failureReason under the separate title.
== 2025.05
Starting from 2025.05, the `failureReason` in the JSON template of the query log, is deprecated and switched off by default.
Use the `errorInfo` entry instead.
This was introduced in 5.25.
To learn more about the JSON object `errorInfo` in the query log, visit the link:https://neo4j.com/docs/operations-manual/current/monitoring/logging/#gql-error-information[Operations manual -> Logging -> GQL error information].
Co-authored-by: Natalia Ivakina <[email protected]>
renetapopova
force-pushed
the
dev-changelog
branch
from
aa823d8 to
8b026b3
Compare
|
This PR includes documentation updates Updated pages: |
3 participants
No description provided.