Sometimes it feels hard to read the log because it’s too much information. A simple
trick to get a more readable log on debug level is to specify a number of extremely
verbose EPiServer loggers to the recommended runtime value WARN. This makes it easier to
debug your own allocations log messages.
EPiServerLog.config
<log4net>
...
<!-- Disable the logger for the cache -->
<logger name="EPiServer.Core.OptimisticCache">
<level value="Warn" />
</logger>
<!-- Disable the logger for the Scheduler -->
<logger name="Microsoft.Samples.Runtime.Remoting.Channels.Pipe.DBG">
<level value="Warn" />
</logger>
<logger name="EPiServer.DataAbstraction.ScheduledJob">
<level value="Warn" />
</logger>
<!-- Disable the logger for friendly URLs -->
<logger name="EPiServer.Web.FriendlyUrlRewriteProvider">
<level value="Warn" />
</logger>
<logger name="EPiServer.Web.UrlRewriteModuleBase">
<level value="Warn" />
</logger>
<logger name="EPiServer.Web.UrlRewriteModule">
<level value="Warn" />
</logger>
<logger name="EPiServer.Web.FriendlyHtmlRewriteToExternal">
<level value="Warn" />
</logger>
<logger name="EPiServer.Web.PermanentLinkMapStore">
<level value="Warn" />
</logger>
<!-- Disable the logger for other heavy logging classes -->
<logger name="EPiServer.Core.PageProviderBase">
<level value="Warn" />
</logger>
<logger name="EPiServer.Web.WebControls.Property">
<level value="Warn" />
</logger>
<logger name="EPiServer.Web.Hosting.VirtualPathVersioningProvider">
<level value="Warn" />
</logger>