You are currently browsing legacy 3.0 version of documentation. Click here to switch to the newest 5.2 version.

We can help you with migration to the latest RavenDB

Contact Us Now
see on GitHub

Troubleshooting: Enabling logging

RavenDB has extensive support for logging, enabling you to figure out exactly what is going on in the server.
By default, logging is turned off, but it can be easily enabled by creating a file called NLog.config in the base directory of a server (remember to restart your server).

Sample log file

<nlog xmlns="" xmlns:xsi="">

			<target xsi:type="SplitGroup">
				<!-- create log files with a max size of 256 MB -->
					<layout xsi:type="CsvLayout">
						<column name="time" layout="${longdate}" />
						<column name="logger" layout="${logger}"/>
						<column name="level" layout="${level}"/>
						<column name="database" layout="${mdc:item=database}"/>
						<column name="threadid" layout="${threadid}" />
						<column name="message" layout="${message}" />
						<column name="exception" layout="${exception:format=tostring}" />
		<!-- supported levels: Off, Fatal, Error, Warn, Info, Debug, Trace -->
 				<logger name="Raven.*" writeTo="AsyncLog" minlevel="Warn" />



To make it even easier for you, we have included NLog.Ignored.config file which just needs to be renamed in the Server directory, inside the distribution package.