You can enable and set trace events in the Admin Interface, on the Diagnostics page for a group. Trace events are used to debug applications. For example, a file log set to Debug would contain many lines of messages whereas a file log set to Emergency would contain the minimum set of messages.Īny trace events are also written to the MarkLogic Server ErrorLog.txt file. The number of messages depends on the system activity and on the log level that you set. These files contain a set of log messages ordered chronologically. The application log files are prefixed with the port number of the App Server corresponding the log file. ~/Library/Application Support/MarkLogic/Data/Logs/_ErrorLog.txt ~/Library/Application Support/MarkLogic/Data/Logs/ErrorLog.txt The following table lists the default location of the file logs on your platform: PlatformĬ:\Program Files\MarkLogic\Data\Logs\ErrorLog.txtĬ:\Program Files\MarkLogic\Data\Logs\_ErrorLog.txt You may have overridden the default location for this directory at installation time. The files are stored in the Logs directory under the MarkLogic Server data directory for your platform.
Additionally, you can access the log files from the Log tab on the main page of the Admin Interface. You may view the current or any archived file log at any time using standard text file viewing tools. The private system file log is maintained as a simple text file, and the application logs are also maintained as simple text files. Viewing the Application and System File Logs Scroll to the top or bottom and click OK.
After the number of log files grows to the value specified in the Keep Log File setting, when a new log file is started, the oldest log file archive is automatically deleted. The private log files are kept in an aging archive.