Logs
This section describes breaking changes for Neo4j logs.
General changes
From the 4.0 version onwards, Neo4j logs have the name of the database to which the log line pertains, printed before the regular text.
For example, [neo4j]
or [system]
.
system
database2019-12-02 22:27:41.820+0000 INFO [o.n.k.d.Database] [system] No check point found in transaction log 2019-12-02 22:27:41.820+0000 INFO [o.n.k.d.Database] [system] Recovery required from position LogPosition{logVersion=0, byteOffset=64} 2019-12-02 22:27:41.820+0000 INFO [o.n.k.r.Recovery] [system] 10% completed 2019-12-02 22:27:41.820+0000 INFO [o.n.k.r.Recovery] [system] 20% completed 2019-12-02 22:27:41.820+0000 INFO [o.n.k.r.Recovery] [system] 30% completed ...
Other log lines might relate to the DBMS as a whole or be logged by a component that lives on a higher level but still operates on a particular database. For example:
CoreDatabaseManager
starting the Neo4j database2019-12-02 22:27:41.964+0000 INFO [c.n.c.c.CoreDatabaseManager] Creating 'neo4j' database. 2019-12-02 22:27:41.967+0000 INFO [c.n.c.c.CoreDatabaseManager] Starting 'neo4j' database. ...
Changes to log configurations per Neo4j version
Configuration setting | Neo4j 4.0 | Neo4j 4.1 | Neo4j 4.2 | Neo4j 4.3 |
---|---|---|---|---|
|
New |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
Removed |
|||
|
Removed |
|||
|
Removed |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
Deprecated |
|||
|
Deprecated |
|||
|
Deprecated |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
New |
|||
|
New |