HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideLegal TermsGitHubNuGetDev CommunitySubmit a ticketLog In

Log into .Net Diagnostics Trace

Describes how to log into .Net Diagnistics Trace.

There are two built-in logger factories for writing log messages from the Optimizely Log API to .NET Diagnostics Trace; the EPiServer.Logging.TraceLoggerFactory and the EPiServer.Logging.TraceSourceLoggerFactory.



In Optimizely Digital Experience Platform (DXP), Optimizely logs are redirected into .NET Diagnostic Trace, as long as the code uses the Optimizely logging abstraction EPiServer.Logging.LogManager. If you are using log4net and deploying in Optimizely DXP, replace log4net with EPiServer.Logging. See also Logging for more information on switching logging APIs.


The EPiServer.Logging.TraceLoggerFactory logger redirects log messages to diagnostics trace.

Optimizely log levelmaps to 
Optimizely Critical and Error Logsystem diagnostics trace error level
Optimizely Warning Log API system diagnostics trace warning level
Optimizely Information Log API system diagnostics trace Information level
Optimizely Debug and Trace Log APInot logged

You enable EPiServer.Logging.TraceLoggerFactory like this:

  <add key="episerver:LoggerFactoryType" 
       value="EPiServer.Logging.TraceLoggerFactory, EPiServer.Framework" />

Or from the episerver.framework section like this:

<episerver.framework loggerFactoryType="EPiServer.Logging.TraceLoggerFactory, EPiServer.Framework">


The EPiServer.Logging.TraceSourceLoggerFactory redirects log messages to diagnostics trace source. In this implementation, each logger name has its source switch trace.

Optimizely log levelmaps to 
Optimizely Critical Log API levelsystem diagnostics trace source critical level
Optimizely Error Log API levelsystem diagnostics trace source error level
Optimizely Warning Log API level system diagnostics trace source warning level
Optimizely Information Log API level system diagnostics trace source Information level
Optimizely Debug and Trace Log APIsystem diagnostics Verbose

You can enable the EPiServer.Logging.TraceSourceLoggerFactory like this:

  <add key="episerver:LoggerFactoryType" 
       value="EPiServer.Logging.TraceSourceLoggerFactory, EPiServer.Framework" />

Or from the <episerver.framework> section like this:

<episerver.framework loggerFactoryType="EPiServer.Logging.TraceSourceLoggerFactory, EPiServer.Framework">

By default, the logging level is set to the Error. If you need to log lower levels than the Error level, configure it in the <system.diagnostics> section like this:

    <source name="logger name" 
            switchName="logger name" 
    <add name="logger name" 
         value="Verbose" />

Register Logger Factory with configuration

To register a logger factory with configuration, you need to add the logger factory type in the <appSettings> section:

  <add key="episerver:LoggerFactoryType" 
       value="the custom logger factory type" />

Or from <episerver.framework> section:

<episerver.framework loggerFactoryType="the custom logger factory type">



The <appsetting> section value always has a higher priority than the <episerver.framework> section value.