Database Logs
In your database Logs tab, GrapheneDB shows the logs natively provided for monitoring purposes. You’ll be able to select the log that you want to retrieve and filter it by Errors or Warnings, but also to choose to show All logs.
We’ve brought to you a great feature to help you with debugging and have quicker insights into what you’re looking for, and it’s called Log Analyzer.
ℹ️ Info
If the database is in a Paused state, logs are not visible. You will need to Resume your database to see the log entries.
Which logs are available to me?
| Singles | Cluster |
|---|---|
| Debug log - The Neo4j debug log. It’s a log of information useful when debugging problems with Neo4j. | Debug log - The Neo4j debug log. It’s a log of information useful when debugging problems with Neo4j. |
| User log - The Neo4j user log, where general information about Neo4j is written. | User log - The Neo4j user log, where general information about Neo4j is written. |
| -------- | Query log - Logs information about queries that run longer than a specified threshold. It helps you analyze long-running queries and does not impact system performance. |
| -------- | Security log - Logs information about security events, such as login attempts, all administration commands and procedures run against the system database, and authorization failures from role-based access control. |
Selecting log type
Singles
Navigate to the drop-down menu in the Logs section, and select either User log or Debug log. For each log, you can use the Scroll to bottom button to navigate to the bottom of the log, or use the Refresh button to retrieve the latest data.
Clusters
Navigate to the drop-down menu in the Logs section, select the Node you’d like to look into logs for, and select one of the following options: User log, Debug log, Query log, Security log. More details on these logs can be found here.
For each log, you can use the Scroll to bottom button to navigate to the bottom of the log, or use the Refresh button to retrieve the latest data.
Filtering by Warnings or Errors
The below details list the messages raised by Neo4j and their severity level.
WARN: Report errors that need attention but are not severe.
ERROR: Report errors that prevent the Neo4j server from running and must be addressed immediately.
To filter the messages in log, navigate to the drop-down menu at the right-hand side, and select one of the options (Show all logs, Show only Warnings, Show only Errors). You can also use the Scroll to bottom or Refresh buttons.
Log Analyzer
The Log Analyzer is a feature designed to help you reduce the time used in locating the most important information. Log Analyzer goes through the log that is loaded and extracts relevant information to map it to an explanation. First of all, it filters warnings, errors, and some interesting info that you can easily switch between.
Additionally, for some logs, we offer an extended explanation related to errors, warnings or info in the log. For example, you’ll be able to see detailed explanations in an event of the database being stopped.
If you click on Navigate button, it will bring you to the exact line in the logs that this extended explanation refers to, being an error, warning, or info, depending on what you’ve selected.
