Understanding the Log Levels
MarkLogic Server sends log messages to both the operating system log and the MarkLogic Server system file log. Additionally, application log messages (messages generated from application code) are sent to the application logs. Depending on how you configure your logging functions, both operating system and file logs may or may not receive the equivalent number of messages. To enhance performance, the system log should receive fewer messages than the MarkLogic Server file log.
MarkLogic Server uses the following log settings, where Finest is the most verbose while Emergency is the least verbose:
Log Level |
Description |
|---|---|
Finest |
Extremely detailed debug level messages. |
Finer |
Very detailed debug level messages. |
Fine |
Detailed debug level messages. |
Debug |
Debug level messages. |
Config |
Configuration messages. |
Info |
Informational messages. This is the default setting. |
Notice |
Normal but significant conditions. |
Warning |
Warning conditions. |
Error |
Error conditions. |
Critical |
Critical conditions. |
Alert |
Immediate action required. |
Emergency |
System is unusable. |
Log file settings are applied on a per-group basis.
By default, the system log for a group is set to Notice while the file log is set to Info. As such, the system log receives fewer log messages than the file log. You may change these settings to suit your needs. It is more efficient to write to the file log than to the system log. It is good practice to run in production with the Debug file log level to get a more detailed record of operations. Log levels more verbose than Debug may result in very large log files and are not recommended for extended periods of time.